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] profiledbootstrap failure: poly-int.h:453:5: error: too many initializers for ‘long int [1]’ (possibly since r14-4339-geaa41a6dc127d8)
Date: Fri, 29 Sep 2023 20:48:03 +0000	[thread overview]
Message-ID: <bug-111642-4-Qdt6WVgTpM@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 #1 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
Looks like this code is all under `#if CHECKING_P` of sorts. A few more
possibly affected entries:

```
$ git grep -P 'poly_int64 \(\d+, \d+\)'

gcc/config/riscv/riscv-selftests.cc:       -BYTES_PER_RISCV_VECTOR * 33,
poly_int64 (207, 0),
gcc/config/riscv/riscv-selftests.cc:       poly_int64 (-207, 0),           
poly_int64 (0, 207),
gcc/config/riscv/riscv-selftests.cc:       poly_int64 (0, -207),           
poly_int64 (5555, 0),
gcc/config/riscv/riscv-selftests.cc:       poly_int64 (0, 5555),           
poly_int64 (4096, 4096),
gcc/config/riscv/riscv-selftests.cc:       poly_int64 (17, 4088),          
poly_int64 (3889, 4104),
gcc/config/riscv/riscv-selftests.cc:       poly_int64 (9317, -88),         
poly_int64 (4, 4),
gcc/config/riscv/riscv-selftests.cc:       poly_int64 (17, 4),      poly_int64
(-7337, 4),
gcc/config/riscv/riscv-selftests.cc:       poly_int64 (219, -1508),        
poly_int64 (2, 2),
gcc/config/riscv/riscv-selftests.cc:       poly_int64 (33, 2),      poly_int64
(-7337, 2),
gcc/config/riscv/riscv-selftests.cc:       poly_int64 (945, -954),         
poly_int64 (1, 1),
gcc/config/riscv/riscv-selftests.cc:       poly_int64 (977, 1),     poly_int64
(-339, 1),
gcc/config/riscv/riscv-selftests.cc:       poly_int64 (44, -1),     poly_int64
(9567, 77),
gcc/config/riscv/riscv.cc:      return poly_int64 (1, 1);

gcc/rtl-tests.cc:  rtx x1 = gen_int_mode (poly_int64 (1, 1), QImode);
gcc/rtl-tests.cc:  rtx x255 = gen_int_mode (poly_int64 (1, 255), QImode);
gcc/rtl-tests.cc:  ASSERT_EQ (x1, gen_int_mode (poly_int64 (1, 1), QImode));
gcc/rtl-tests.cc:  ASSERT_NE (x1, gen_int_mode (poly_int64 (1, 1), HImode));
gcc/rtl-tests.cc:  ASSERT_KNOWN_EQ (const_poly_int_value (x1), poly_int64 (1,
1));
gcc/rtl-tests.cc:  ASSERT_KNOWN_EQ (rtx_to_poly_int64 (x1), poly_int64 (1, 1));
gcc/rtl-tests.cc:  ASSERT_MAYBE_NE (rtx_to_poly_int64 (x255), poly_int64 (1,
255));
gcc/rtl-tests.cc:  rtx offset1 = gen_int_mode (poly_int64 (9, 11), Pmode);
gcc/rtl-tests.cc:  ASSERT_RTX_EQ (plus_constant (Pmode, symbol, poly_int64 (9,
11)), sum1);
gcc/rtl-tests.cc:  rtx offset2 = gen_int_mode (poly_int64 (12, 20), Pmode);
gcc/rtl-tests.cc:  ASSERT_RTX_EQ (plus_constant (Pmode, sum1, poly_int64 (3,
9)), sum2);

gcc/simplify-rtx.cc:  rtx x1 = gen_int_mode (poly_int64 (1, 1), QImode);
gcc/simplify-rtx.cc:  rtx x4 = gen_int_mode (poly_int64 (5, 4), QImode);
gcc/simplify-rtx.cc:  rtx x5 = gen_int_mode (poly_int64 (30, 24), QImode);
gcc/simplify-rtx.cc:  rtx x6 = gen_int_mode (poly_int64 (20, 16), QImode);
gcc/simplify-rtx.cc:  rtx x7 = gen_int_mode (poly_int64 (7, 4), QImode);
gcc/simplify-rtx.cc:  rtx x8 = gen_int_mode (poly_int64 (30, 24), HImode);
```

  reply	other threads:[~2023-09-29 20:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29 19:18 [Bug bootstrap/111642] New: " slyfox at gcc dot gnu.org
2023-09-29 20:48 ` slyfox at gcc dot gnu.org [this message]
2023-09-30  6:59 ` [Bug bootstrap/111642] " 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
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-Qdt6WVgTpM@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).