public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Mon, 02 Oct 2023 06:21:14 +0000 [thread overview]
Message-ID: <bug-111642-4-dr7ew1cs5c@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
--- Comment #17 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Richard Sandiford <rsandifo@gcc.gnu.org>:
https://gcc.gnu.org/g:e465e5e4a969334f64cf0d6611de5273d73ea732
commit r14-4359-ge465e5e4a969334f64cf0d6611de5273d73ea732
Author: Richard Sandiford <richard.sandiford@arm.com>
Date: Mon Oct 2 07:20:45 2023 +0100
Fix profiledbootstrap poly_int fallout [PR111642]
rtl-tests.cc and simplify-rtx.cc used partial specialisation
to try to restrict the NUM_POLY_INT_COEFFS>1 tests without
resorting to preprocessor tests. That now triggers an error
in some configurations, since the NUM_POLY_INT_COEFFS>1 tests
used the global poly_int64, whose definition does not depend
on the template parameter.
This patch uses local types that do depend on the template parameter.
gcc/
PR bootstrap/111642
* rtl-tests.cc (const_poly_int_tests<N>::run): Use a local
poly_int64 typedef.
* simplify-rtx.cc (simplify_const_poly_int_tests<N>::run):
Likewise.
next prev parent reply other threads:[~2023-10-02 6:21 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
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 [this message]
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-dr7ew1cs5c@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).