[Bug c/35092] Global variable reference not resolved with -Os option

2008-02-06 Thread steven at gcc dot gnu dot org
--- Comment #5 from steven at gcc dot gnu dot org 2008-02-06 09:05 --- There was -Wnull-dereference once. I don't know if it still exists. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35092

[Bug c/35092] Global variable reference not resolved with -Os option

2008-02-05 Thread lee_merrill at yahoo dot com
--- Comment #4 from lee_merrill at yahoo dot com 2008-02-05 19:58 --- It might be good to have the compiler issue a warning for such? It's neat that it can tell that it's got a zero pointer... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35092

[Bug c/35092] Global variable reference not resolved with -Os option

2008-02-05 Thread rguenth at gcc dot gnu dot org
--- Comment #3 from rguenth at gcc dot gnu dot org 2008-02-05 16:57 --- Thus, invalid. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added Status|U

[Bug c/35092] Global variable reference not resolved with -Os option

2008-02-05 Thread pluto at agmk dot net
--- Comment #2 from pluto at agmk dot net 2008-02-05 16:33 --- (In reply to comment #0) it's not a gcc bug, it's a null pointer dereference. > while (1) { > if (ctrl) { > (...) > lxTraceCopy(cuSub->traceTag, ctrl->ctrlPath, ... > } else if (p

[Bug c/35092] Global variable reference not resolved with -Os option

2008-02-05 Thread lee_merrill at yahoo dot com
--- Comment #1 from lee_merrill at yahoo dot com 2008-02-05 15:51 --- Created an attachment (id=15101) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15101&action=view) The source code for causing the described problem Type "make" and then run "btifc" to cause a core dump. The disa