public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/111642] [14 Regression] bootstrap4 or profiledbootstrap failure: poly-int.h:453:5: error: too many initializers for ‘long int [1]’ (possibly since r14-4339-geaa41a6dc127d8)
Date: Sat, 30 Sep 2023 12:34:32 +0000 [thread overview]
Message-ID: <bug-111642-4-jOpZ4Ilwld@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111642-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111642
Sergei Trofimovich <slyfox at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |111647
--- Comment #6 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
(In reply to Sergei Trofimovich from comment #5)
> I'll try to extract smaller example.
Got the following, but I'm not sure it's valid C++:
struct poly_int {
template <typename...> constexpr poly_int() : poly_int() {}
};
template <int> void run() { poly_int(); }
Filed PR111647 and will try to extract something less invalid.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111647
[Bug 111647] g++ accepts different c++ on -fchecking= anf checking=2
next prev parent reply other threads:[~2023-09-30 12:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 19:18 [Bug bootstrap/111642] New: [14 Regression] " slyfox at gcc dot gnu.org
2023-09-29 20:48 ` [Bug bootstrap/111642] " slyfox at gcc dot gnu.org
2023-09-30 6:59 ` eike@sf-mail.de
2023-09-30 7:26 ` [Bug bootstrap/111642] [14 Regression] bootstrap4 or " slyfox at gcc dot gnu.org
2023-09-30 10:32 ` slyfox at gcc dot gnu.org
2023-09-30 10:45 ` slyfox at gcc dot gnu.org
2023-09-30 12:34 ` slyfox at gcc dot gnu.org [this message]
2023-09-30 14:57 ` slyfox at gcc dot gnu.org
2023-09-30 19:25 ` slyfox at gcc dot gnu.org
2023-09-30 20:27 ` arsen at gcc dot gnu.org
2023-09-30 20:35 ` arsen at gcc dot gnu.org
2023-09-30 20:51 ` slyfox at gcc dot gnu.org
2023-10-01 20:07 ` pinskia at gcc dot gnu.org
2023-10-01 21:33 ` rsandifo at gcc dot gnu.org
2023-10-02 2:52 ` slyfox at gcc dot gnu.org
2023-10-02 4:40 ` xry111 at gcc dot gnu.org
2023-10-02 4:44 ` xry111 at gcc dot gnu.org
2023-10-02 6:21 ` cvs-commit at gcc dot gnu.org
2023-10-02 6:23 ` rsandifo 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-111642-4-jOpZ4Ilwld@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).