On Wed, Nov 06, 2013 at 02:20:18PM +, Ian Jackson wrote:
Tom Lane writes (Re: Old GCC bug affecting postgresql error handling):
Ian Jackson ijack...@chiark.greenend.org.uk writes:
I wasn't able to do a test of the actual current postgresql with a
current Debian compiler. The original
Tom Lane writes (Re: Old GCC bug affecting postgresql error handling):
Ian Jackson ijack...@chiark.greenend.org.uk writes:
Alex Deiter appears to have tried to report this to gcc upstream:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29968
However, the test program in that bugzilla report
Ian Jackson ijack...@chiark.greenend.org.uk 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
Tom Lane writes (Re: Old GCC bug affecting postgresql error handling):
Ian Jackson ijack...@chiark.greenend.org.uk writes:
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
I recently came across this bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616180
This relates to a gcc optimisation bug affecting postgresql error
handling. (It was reported there in Debian on Sparc in gcc 4.x.)
Assumign that the ereport function/macro used there doesn't
Ian Jackson ijack...@chiark.greenend.org.uk writes:
I recently came across this bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616180
This relates to a gcc optimisation bug affecting postgresql error
handling. (It was reported there in Debian on Sparc in gcc 4.x.)
Assumign
6 matches
Mail list logo
