public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steve_green at qq dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/101710] New: Sometimes constexpr cannot be used as constexpr
Date: Sun, 01 Aug 2021 02:11:18 +0000 [thread overview]
Message-ID: <bug-101710-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101710
Bug ID: 101710
Summary: Sometimes constexpr cannot be used as constexpr
Product: gcc
Version: 11.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: steve_green at qq dot com
Target Milestone: ---
Created attachment 51231
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51231&action=edit
.ii file & .s file & output
I want to make a minimal reproduction of this ICE, but it seems I can't
So allow me to post a link to the project, sorry
You can try to compile this file
https://github.com/ELC-lang/ELC/blob/master/parts/header_file/test/forICE.cpp
In MSVC, the compilation of this file will stop due to some ICE, but it is
different from ICEs that GCC have
The problem with GCC is that all "error: expected primary-expression before ‘X’
token" can be compiled in MSVC
next reply other threads:[~2021-08-01 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 2:11 steve_green at qq dot com [this message]
2021-08-01 2:17 ` [Bug c++/101710] " steve_green at qq dot com
2021-08-01 8:22 ` pinskia at gcc dot gnu.org
2021-08-01 8:25 ` pinskia at gcc dot gnu.org
2021-08-01 8:26 ` steve_green at qq dot com
2021-08-01 8:28 ` steve_green at qq dot com
2021-08-01 8:42 ` pinskia at gcc dot gnu.org
2021-08-01 8:54 ` pinskia at gcc dot gnu.org
2021-08-01 8:59 ` steve_green at qq dot com
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-101710-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: link
Be 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).