public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/51433] constexpr caching leads to incorrect dynamic initialization Date: Tue, 10 Jan 2012 14:38:00 -0000 [thread overview] Message-ID: <bug-51433-4-eTbiodGiaf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51433-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51433 --- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> 2012-01-10 14:37:30 UTC --- Author: jason Date: Tue Jan 10 14:37:26 2012 New Revision: 183065 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183065 Log: PR c++/51433 * semantics.c (cxx_eval_call_expression): Always retry previously non-constant expressions. Added: trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-cache1.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/semantics.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2012-01-10 14:38 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-06 5:19 [Bug c++/51433] New: " richard-gccbugzilla at metafoo dot co.uk 2012-01-07 22:36 ` [Bug c++/51433] " pinskia at gcc dot gnu.org 2012-01-10 14:38 ` jason at gcc dot gnu.org [this message] 2012-01-10 14:39 ` jason at gcc dot gnu.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-51433-4-eTbiodGiaf@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).