public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marc.glisse at normalesup dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46336] New: [C++0X] ICE on invalid: in register_constexpr_fundef, at cp/semantics.c:5571 Date: Sat, 06 Nov 2010 23:41:00 -0000 [thread overview] Message-ID: <bug-46336-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46336 Summary: [C++0X] ICE on invalid: in register_constexpr_fundef, at cp/semantics.c:5571 Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: marc.glisse@normalesup.org This is an ICE on invalid code that I hit while trying to reduce an example for a more important bug. extern "C" { enum A { }; inline constexpr A f(A a, A b) { return A(static_cast<int>(a) & static_cast<int>(b)); } enum B { }; inline constexpr B f(B a, B b) { return B(static_cast<int>(a) & static_cast<int>(b)); } } 4.cc: In function ‘constexpr B f(B, B)’: 4.cc:8:13: error: declaration of C function ‘constexpr B f(B, B)’ conflicts with 4.cc:4:3: error: previous declaration ‘constexpr A f(A, A)’ here 4.cc: In function ‘constexpr B f(B, B)’: 4.cc:9:58: internal compiler error: in register_constexpr_fundef, at cp/semantics.c:5571
next reply other threads:[~2010-11-06 23:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-06 23:41 marc.glisse at normalesup dot org [this message] 2010-11-07 11:13 ` [Bug c++/46336] " paolo.carlini at oracle dot com 2011-03-16 21:05 ` jason at gcc dot gnu.org 2011-03-17 2:36 ` jason at gcc dot gnu.org 2011-03-17 2:40 ` 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-46336-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).