| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Mark Jewiss <mark(dot)jewiss(at)knowledge(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Re: [GENERAL] Version 7.0 beta problem |
| Date: | 2000-03-07 06:55:21 |
| Message-ID: | 19107.952412121@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Mark Jewiss writes:
>> mainloop.c:43: warning: variable `successResult' might be clobbered by `longjmp' or `vfork'
> I thought I had shut up those warnings by making the variables in question
> volatile. There's no need to worry about them since they're re-initialized
> right after the longjmp, but does anyone know how to shut up the compiler?
That *should* shut up these warnings. Maybe Mark is trying a slightly
back-dated beta version? I know you didn't have the "volatile"s in
there a few days ago.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-03-07 06:58:22 | Re: BIT/BIT VARYING names (was Re: [HACKERS] Beta for 4:30AST) |
| Previous Message | Tom Lane | 2000-03-07 06:51:32 | Re: [BUGS] grant/revoke bug with delete/update |