This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp
- From: "dnovillo at acm dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 May 2007 13:10:16 -0000
- Subject: [Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp
- References: <bug-31862-87@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #1 from dnovillo at acm dot org 2007-05-08 14:10 -------
Subject: Re: New: Loop IM and other optimizations harmful for -fopenmp
On 8 May 2007 07:59:03 -0000, jakub at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
> See http://openmp.org/pipermail/omp/2007/000840.html
> and the rest of the lengthy threads:
Yes, I've been following the thread and I agree that we need to do
something to avoid the problem. The real solution is, unfortunately,
quite a bit of work.
In the meantime, we should probably annotate the shared variables and
consider them volatile. This should prevent most optimizers from
messing things up inadvertently.
This should be done within OMP regions. Orphaned functions may become
a problem, so this should be implemented as an IPA pass.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31862