public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "keesjan at cobalt dot et dot tudelft dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/40389] New: optimizer bug (possibly) Date: Tue, 09 Jun 2009 15:46:00 -0000 [thread overview] Message-ID: <bug-40389-17817@http.gcc.gnu.org/bugzilla/> (raw) After compiling a particular C++ program (see attachment) both with and without the -O option, the program produces different results. When compiled with -O, the program produces the output "(nil)", whereas when compiled without any options, the program prints a non-null pointer (which may of course vary between runs). The program is only 121 lines long, and was obtained by reducing an initial set of over 30.000 lines of code until no further reduction seemed to be possible without suppressing the problem. For example, by moving the static variable " fs_active_handle" into the main function, the problem "magically" disappears. Also, when adding printf-statements to the functions, or by manually inlining certain constructs, the problem disappears. Due to the immense reduction of the code, the semantics of the code may not seem clear anymore (that is, I am myself not sure what this program is supposed to do anymore), but the problem with the optimizer clearly shows. I have tried to use the tool valgrind to see if something illegal is happening wrt copy-constructors/assignment operators (despite close inspection), but this does not seem to be the case. -- Summary: optimizer bug (possibly) Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: critical Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: keesjan at cobalt dot et dot tudelft dot nl GCC build triplet: x86_64-unknown-linux-gnu GCC host triplet: x86_64-unknown-linux-gnu GCC target triplet: x86_64-unknown-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40389
next reply other threads:[~2009-06-09 15:46 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-09 15:46 keesjan at cobalt dot et dot tudelft dot nl [this message] 2009-06-09 15:49 ` [Bug c++/40389] " keesjan at cobalt dot et dot tudelft dot nl 2009-06-09 17:11 ` jakub at gcc dot gnu dot org 2009-06-09 20:25 ` rguenth at gcc dot gnu dot org 2009-06-09 21:22 ` jakub at gcc dot gnu dot org 2009-06-09 21:27 ` rguenth at gcc dot gnu dot org 2009-06-09 21:31 ` pinskia at gcc dot gnu dot org 2009-06-09 21:44 ` jakub at gcc dot gnu dot org 2009-06-10 19:37 ` jason at gcc dot gnu dot org 2009-06-10 19:40 ` jason at gcc dot gnu dot org 2009-06-10 19:47 ` rguenth at gcc dot gnu dot org 2009-06-10 20:13 ` jason at gcc dot gnu dot org 2009-06-10 20:58 ` jason at gcc dot gnu dot org 2009-06-10 20:59 ` rguenth at gcc dot gnu dot org 2009-06-10 21:27 ` jakub at gcc dot gnu dot org 2009-06-10 21:28 ` jakub at gcc dot gnu dot org 2009-06-10 21:29 ` rguenth at gcc dot gnu dot org 2009-06-12 17:30 ` jason at redhat dot com 2009-06-12 18:58 ` jakub at gcc dot gnu dot org 2009-06-13 17:02 ` rguenth at gcc dot gnu dot org 2009-06-13 19:23 ` pinskia at gcc dot gnu dot org 2009-06-13 19:31 ` rguenth at gcc dot gnu dot org 2009-06-13 22:58 ` rguenth at gcc dot gnu dot org 2009-06-13 22:58 ` rguenth at gcc dot gnu dot org 2009-06-14 15:40 ` jason at redhat dot com 2009-06-14 15:40 ` jason at redhat dot com 2009-06-14 15:42 ` rguenther at suse dot de 2009-06-17 10:29 ` rguenth at gcc dot gnu dot org 2009-06-17 10:34 ` rguenth at gcc dot gnu dot org 2009-06-17 12:03 ` rguenth at gcc dot gnu dot org 2009-06-17 12:04 ` rguenth at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-40389-17817@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).