[Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp

2021-07-20 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31862 Andrew Pinski changed: What|Removed |Added Component|middle-end |tree-optimization --- Comment #26 from A

[Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp

2007-05-08 Thread pinskia at gmail dot com
--- Comment #8 from pinskia at gmail dot com 2007-05-08 19:45 --- Subject: Re: Loop IM and other optimizations harmful for -fopenmp On 8 May 2007 18:08:26 -, jakub at gcc dot gnu dot org <[EMAIL PROTECTED]> wrote: > > > --- Comment #7 from jakub at gcc dot gnu dot org 2007-05-

[Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp

2007-05-08 Thread jakub at gcc dot gnu dot org
--- Comment #7 from jakub at gcc dot gnu dot org 2007-05-08 19:08 --- This really is not specific to OpenMP, I believe the following is valid threaded program: #define _XOPEN_SOURCE 600 #include #include int v; pthread_mutex_t m = PTHREAD_MUTEX_INITIALIZER; pthread_barrier_t b; void

[Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp

2007-05-08 Thread pinskia at gmail dot com
--- Comment #6 from pinskia at gmail dot com 2007-05-08 15:59 --- Subject: Re: Loop IM and other optimizations harmful for -fopenmp On 8 May 2007 14:44:16 -, dnovillo at acm dot org <[EMAIL PROTECTED]> wrote: > The original code did not have a race condition. The compiler > transf

Re: [Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp

2007-05-08 Thread Andrew Pinski
On 8 May 2007 14:44:16 -, dnovillo at acm dot org <[EMAIL PROTECTED]> wrote: The original code did not have a race condition. The compiler transformations introduced a race-condition. This *is* a compiler bug. Actually the original code has a race condition, if another thread is reading

[Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp

2007-05-08 Thread dnovillo at acm dot org
--- Comment #5 from dnovillo at acm dot org 2007-05-08 15:44 --- Subject: Re: Loop IM and other optimizations harmful for -fopenmp On 8 May 2007 14:37:05 -, rguenth at gcc dot gnu dot org <[EMAIL PROTECTED]> wrote: > OMP is not a good generic programming model for threaded code.

[Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp

2007-05-08 Thread dnovillo at acm dot org
--- Comment #4 from dnovillo at acm dot org 2007-05-08 15:39 --- Subject: Re: Loop IM and other optimizations harmful for -fopenmp On 8 May 2007 14:30:45 -, pinskia at gcc dot gnu dot org <[EMAIL PROTECTED]> wrote: > --- Comment #2 from pinskia at gcc dot gnu dot org 2007-05-

[Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp

2007-05-08 Thread rguenth at gcc dot gnu dot org
--- Comment #3 from rguenth at gcc dot gnu dot org 2007-05-08 15:37 --- OMP is not a good generic programming model for threaded code. Exactly because of this issues. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31862

[Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp

2007-05-08 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-05-08 15:30 --- WTF, this is just sad we have to disable optimizations because openmp folks don't know how to program threaded code. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31862

[Bug tree-optimization/31862] Loop IM and other optimizations harmful for -fopenmp

2007-05-08 Thread dnovillo at acm 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 -, jakub at gcc dot gnu dot org <[EMAIL PROTECTED]> wrote: > See http://openmp.org/pipermail/omp/2007/000840.html > and the