This is the mail archive of the
mailing list for the GCC project.
Re: Optimization of conditional access to globals: thread-unsafe?
- From: Jason Merrill <jason at redhat dot com>
- To: Ian Lance Taylor <iant at google dot com>
- Cc: Diego Novillo <dnovillo at google dot com>, Michael Matz <matz at suse dot de>, gcc at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Wed, 31 Oct 2007 16:40:22 -0400
- Subject: Re: Optimization of conditional access to globals: thread-unsafe?
- Newsgroups: gmane.comp.gcc.devel, gmane.comp.gcc.patches
- References: <firstname.lastname@example.org> <email@example.com> <20071026143334.GA5041@moonlight.home> <firstname.lastname@example.org> <20071026155101.GB5041@moonlight.home> <016201c817e9$5454edd0$2e08a8c0@CAM.ARTIMI.COM> <20071026161739.GC5041@moonlight.home> <Pine.LNX.email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
Ian Lance Taylor wrote:
It appears that the draft C++0x memory model prohibits speculative
Therefore I now think we should aim toward prohibiting them
I agree, or perhaps unless the user specifies a flag like
-fthread-unsafe-opts or something.
That memory model is just a draft.
It was voted into the C++ standard working paper at the last meeting.
And the C committee has expressed interest in adopting it, or something
similar, as well.