Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140512121346.GZ26358@brightrain.aerifal.cx>
Date: Mon, 12 May 2014 08:13:46 -0400
From: Rich Felker <dalias@...c.org>
To: James Cloos <cloos@...loos.com>
Cc: Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	musl@...ts.openwall.com
Subject: Re: Broken GCC versions: 4.8.2 and 4.9.0

On Sun, May 11, 2014 at 04:08:37PM -0400, James Cloos wrote:
> >>>>> "RF" == Rich Felker <dalias@...c.org> writes:
> 
> RF> I've tested it on gcc.godbolt.org and others have tested with local
> RF> gcc 4.8.2 and 4.9.0, probably distro-provided (I didn't ask).
> 
> I just tried debian-sid's 4.9.  That does show the bug.  As does their
> gcc-snapshot version (a 4.10 pre).
> 
> Perhaps the distro(s) which have the bug with 4.8.2 backported the commit
> where the bug first occurs?

Indeed, I think all the systems tested have been Debian-based (Debian
or Ubuntu) and a quick check shows that their gcc-4.8 package, despite
calling itself 4.8.2, is actually sync'd with the upstream 4.8 svn
branch... There's a giant patch
gcc-4.8-4.8.2/debian/patches/svn-updates.diff in the debian diff for
the package, which contains everything between 4.8.2 release and the
svn head. This is where the bug can probably be found.

In short, Debian/Ubuntu's "gcc-4.8" package is essentially gcc 4.9.0.

Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.