public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56438] [4.8 regression] ICE in value_dependent_expression_p, at cp/pt.c:19551 Date: Mon, 25 Feb 2013 08:17:00 -0000 [thread overview] Message-ID: <bug-56438-4-rtMjk9FxpM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56438-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56438 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-02-25 08:17:04 UTC --- It is the maybe_constant_value now called from C++98 mode of null_ptr_cst_p. The ICE is on: 19551 /* If there are no operands, it must be an expression such 19552 as "int()". This should not happen for aggregate types 19553 because it would form non-constant expressions. */ 19554 gcc_assert (cxx_dialect >= cxx0x 19555 || INTEGRAL_OR_ENUMERATION_TYPE_P (type)); As we now call maybe_constant_value even on what isn't known to be a constant expression, can we drop this assertion, or set some flag in maybe_constant_value to allow this and reset it back afterwards?
next prev parent reply other threads:[~2013-02-25 8:17 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-24 23:56 [Bug c++/56438] New: " manisandro at gmail dot com 2013-02-25 8:10 ` [Bug c++/56438] " jakub at gcc dot gnu.org 2013-02-25 8:17 ` jakub at gcc dot gnu.org [this message] 2013-02-26 4:28 ` jason at gcc dot gnu.org 2013-02-26 4:30 ` jason at gcc dot gnu.org 2014-03-01 9:58 ` trippels 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-56438-4-rtMjk9FxpM@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).