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++/56481] [4.8 Regression] endless loop compiling a C++ file Date: Thu, 28 Feb 2013 20:22:00 -0000 [thread overview] Message-ID: <bug-56481-4-qtWPKVKZ0i@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56481-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56481 --- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> 2013-02-28 20:21:36 UTC --- Author: jason Date: Thu Feb 28 20:21:23 2013 New Revision: 196358 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=196358 Log: PR c++/56481 * semantics.c (potential_constant_expression_1): Use cxx_eval_outermost_constant_expr rather than maybe_constant_value. Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/semantics.c
next prev parent reply other threads:[~2013-02-28 20:22 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-28 10:32 [Bug c++/56481] New: " doko at gcc dot gnu.org 2013-02-28 12:00 ` [Bug c++/56481] " jakub at gcc dot gnu.org 2013-02-28 16:58 ` jason at gcc dot gnu.org 2013-02-28 17:36 ` jakub at gcc dot gnu.org 2013-02-28 20:22 ` jason at gcc dot gnu.org [this message] 2013-02-28 20:37 ` jason at gcc dot gnu.org 2013-02-28 20:45 ` jakub at gcc dot gnu.org 2013-03-17 2:38 ` 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-56481-4-qtWPKVKZ0i@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).