On Wed, Nov 06, 2013 at 02:20:18PM +0000, 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 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.
>
> Indeed. If I had the time and resources I might try seeing if current
> postgresql can be persuaded to re-exhibit this bug with a modern
> compiler by reverting some of the return statements put in as a
> workaround for this bug. But I don't.
>
I have just tried on sparc64 machine with a sparc64 chroot. The problem
is still reproducible with gcc 4.4, but not with latest versions (tested
with 4.6 and 4.8). Given gcc 4.8 is the default on sparc64, I guess we
can really consider the problem as fixed.
Aurelien
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
