------- Comment #19 from dnovillo at google dot com 2009-02-25 16:12 -------
Subject: Re: Loop IM and other optimizations harmful
for -fopenmp
On Wed, Feb 25, 2009 at 11:06, davids at webmaster dot com
<gcc-bugzi...@gcc.gnu.org> wrote:
>
>
> ------- Comment #18 from davids at webmaster dot com  2009-02-25 16:06
> -------
> This is a real bug. There is simply no way to write correct threaded code if
> the compiler is free to read a variable and write it back when the code didn't
> specifically tell it to.
Yes. Unless we build an actual concurrent data flow and adapt the
optimizers for these programs, we will never get it right. The best
approach in these cases is to tell the optimizers to back off
completely. After all the code has completely different semantics
from what they are ready to handle.
Diego.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31862
