This is the mail archive of the
mailing list for the GCC project.
Re: Is gcc thread-unsafe?
- From: Andrew Haley <aph-gcc at littlepinkcloud dot COM>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: David Schwartz <davids at webmaster dot com>, gcc at gcc dot gnu dot org
- Date: Tue, 30 Oct 2007 10:31:17 +0000
- Subject: Re: Is gcc thread-unsafe?
- References: <firstname.lastname@example.org> <MDEHLPKNGKAHNMBLJOLKCELIHMAC.email@example.com> <firstname.lastname@example.org> <20071030102836.GL5451@devserv.devel.redhat.com>
Jakub Jelinek writes:
> On Tue, Oct 30, 2007 at 10:20:34AM +0000, Andrew Haley wrote:
> > That's what the proposed standard language says, kinda-sorta. There's
> > an informal description at
> > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2338.html.
> > Anyway, we have fixed this bug and are committing it to all open gcc
> > branches. Credit to Ian Taylor for writing the patch.
> To be precise, it was fixed in one of the optimization passes, there
> are still others (e.g. loop invariant motion).
Ah, thanks for clarifying that. Do you have a test case?