public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "eric-gcc at omnifarious dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/50087] New: Weird optimization anomoly with constexpr Date: Mon, 15 Aug 2011 12:49:00 -0000 [thread overview] Message-ID: <bug-50087-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50087 Bug #: 50087 Summary: Weird optimization anomoly with constexpr Classification: Unclassified Product: gcc Version: 4.6.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: eric-gcc@omnifarious.org Created attachment 25014 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25014 runs_too_long runs in a very short period of time I have two nearly identical programs. In one (small.joe.cpp), a function called 'runs_too_long' does not run too long. It is compiled down to returning a constant value. In another, very slightly different program (small-nojoe.cpp), the function 'runs_too_long' does indeed run too long. It, in fact will not complete in any reasonable length of time.
next reply other threads:[~2011-08-15 12:48 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-15 12:49 eric-gcc at omnifarious dot org [this message] 2011-08-15 13:02 ` [Bug c++/50087] " eric-gcc at omnifarious dot org 2011-08-15 13:39 ` [Bug c++/50087] [C++0x] Weird optimization anomaly " paolo.carlini at oracle dot com 2011-08-16 21:49 ` jason at gcc dot gnu.org 2011-08-16 21:52 ` paolo.carlini at oracle dot com 2011-09-02 20:58 ` eric-bugs at omnifarious dot org 2011-09-03 0:49 ` jason at gcc dot gnu.org 2011-09-13 22:55 ` eric-gcc at omnifarious 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-50087-4@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).