Ian Jackson <[email protected]> writes:
> Tom Lane writes ("Re: Old GCC bug affecting postgresql error handling"):
>> I wonder whether the gcc folk reconsidered and fixed the problem
>> somewhere between 4.1.x and 4.4.x. I've seen them reverse course
>> before on what was or wasn't a bug.
> I wasn't able to do a test of the actual current postgresql with a
> current Debian compiler. The original report is on sparc64 which is a
> bit difficult as I can't find any sparc64 porter box.
Well, I certainly hope current Postgres would not show the bug, regardless
of gcc's whims ;-). We have those extra return statements in there now,
and also in current sources there's been an attempt to teach the compiler
that ereport(ERROR) doesn't return anyway, via __builtin_unreachable()
or local equivalent. I remain concerned that there may be other places
exhibiting bugs with the same cause, but I'm pretty sure we've masked the
division-by-zero symptom.
regards, tom lane
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
