[Bug c/41206] Segmentation fault from two "#pragma GCC optimize" lines

2021-11-28 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41206
Bug 41206 depends on bug 37565, which changed state.

Bug 37565 Summary: __optimize__  attribute doesn't work correctly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37565

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

[Bug c/41206] Segmentation fault from two "#pragma GCC optimize" lines

2013-10-21 Thread mpolacek at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41206

Marek Polacek  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||mpolacek at gcc dot gnu.org
 Resolution|--- |FIXED

--- Comment #6 from Marek Polacek  ---
Seems to be fixed, closing.


[Bug c/41206] Segmentation fault from two "#pragma GCC optimize" lines

2010-11-05 Thread froydnj at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41206

Nathan Froyd  changed:

   What|Removed |Added

 CC||froydnj at gcc dot gnu.org

--- Comment #5 from Nathan Froyd  2010-11-05 
17:46:18 UTC ---
I no longer see this error with current mainline.


[Bug c/41206] Segmentation fault from two "#pragma GCC optimize" lines

2009-09-21 Thread ktietz at gcc dot gnu dot org


--- Comment #4 from ktietz at gcc dot gnu dot org  2009-09-21 17:36 ---
By using this code and compiling with gcc test.c -O2 I can reproduce this for
i686-pc-linux, x86_64-pc-linux, x86_64-pc-mingw32, and for i686-pc-mingw32.


-- 

ktietz at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2009-09-21 17:36:49
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41206



[Bug c/41206] Segmentation fault from two "#pragma GCC optimize" lines

2009-08-31 Thread benhoyt+gccbugzilla at gmail dot com


--- Comment #3 from benhoyt+gccbugzilla at gmail dot com  2009-09-01 03:25 
---
(In reply to comment #2)
> It only shows [your email address] on the web interface.
> The mail that goes out is mangled.

Isn't that the opposite of what it should be? The web interface is public,
visible by spammers and email address harvesters, whereas the email only goes
to gcc-bugs@gcc.gnu.org or private individuals.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41206



[Bug c/41206] Segmentation fault from two "#pragma GCC optimize" lines

2009-08-31 Thread pinskia at gcc dot gnu dot org


--- Comment #2 from pinskia at gcc dot gnu dot org  2009-09-01 03:21 ---
(In reply to comment #1)
> Just an off-topic comment from a first-time bug reporter ... With spam the
> problem that it is, why does GCC Bugzilla show my email address in the clear
> and unmunged when I report a bug?

It only shows it on the web interface.  The mail that goes out is mangled.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41206



[Bug c/41206] Segmentation fault from two "#pragma GCC optimize" lines

2009-08-31 Thread benhoyt+gccbugzilla at gmail dot com


--- Comment #1 from benhoyt+gccbugzilla at gmail dot com  2009-09-01 02:04 
---
Just an off-topic comment from a first-time bug reporter ... With spam the
problem that it is, why does GCC Bugzilla show my email address in the clear
and unmunged when I report a bug?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41206