public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "malat at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111268] New: internal compiler error: in to_constant, at poly-int.h:504
Date: Fri, 01 Sep 2023 12:56:02 +0000 [thread overview]
Message-ID: <bug-111268-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111268
Bug ID: 111268
Summary: internal compiler error: in to_constant, at
poly-int.h:504
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: malat at debian dot org
Target Milestone: ---
I am well aware of PR/109176 but it looks somewhat different. Reporting it
here:
ref:
*
https://buildd.debian.org/status/fetch.php?pkg=highway&arch=arm64&ver=1.0.8%7Egit20230830.fed142a-1&stamp=1693567540&raw=0
In file included from /<<PKGBUILDDIR>>/hwy/foreach_target.h:207,
from /<<PKGBUILDDIR>>/hwy/tests/shift_test.cc:18:
/<<PKGBUILDDIR>>/hwy/tests/shift_test.cc: In function 'void
hwy::N_SVE2_128::TestRotateRight::operator()(T, D) [with T = long unsigned int;
D = hwy::N_SVE2_128::Simd<long unsigned int, 2, 0>]':
/<<PKGBUILDDIR>>/hwy/tests/shift_test.cc:157:34: internal compiler error: in
to_constant, at poly-int.h:504
0xe96ec3 internal_error(char const*, ...)
???:0
0xe81f63 fancy_abort(char const*, int, char const*)
???:0
0x19f174f vect_slp_analyze_operations(vec_info*)
???:0
0x17b9f63 vect_slp_function(function*)
???:0
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-snapshot/README.Bugs> for instructions.
next reply other threads:[~2023-09-01 12:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 12:56 malat at debian dot org [this message]
2023-09-01 12:57 ` [Bug target/111268] " malat at debian dot org
2023-09-01 12:57 ` malat at debian dot org
2023-09-01 12:59 ` malat at debian dot org
2023-09-02 3:22 ` [Bug tree-optimization/111268] [14 Regression] " pinskia at gcc dot gnu.org
2023-09-05 9:19 ` malat at debian dot org
2023-09-06 1:57 ` pinskia at gcc dot gnu.org
2023-09-06 2:15 ` pinskia at gcc dot gnu.org
2023-09-07 2:11 ` pinskia at gcc dot gnu.org
2023-10-17 12:44 ` rguenth at gcc dot gnu.org
2023-10-17 12:48 ` rguenth at gcc dot gnu.org
2024-01-04 8:16 ` pinskia at gcc dot gnu.org
2024-01-05 14:17 ` jakub at gcc dot gnu.org
2024-01-05 22:33 ` [Bug tree-optimization/111268] [11/12/13/14 " pinskia at gcc dot gnu.org
2024-01-16 11:41 ` jakub at gcc dot gnu.org
2024-01-18 18:33 ` pinskia at gcc dot gnu.org
2024-01-30 14:45 ` ricbal02 at gcc dot gnu.org
2024-02-01 17:08 ` ricbal02 at gcc dot gnu.org
2024-02-01 17:10 ` ricbal02 at gcc dot gnu.org
2024-02-01 17:20 ` cvs-commit at gcc dot gnu.org
2024-02-01 17:24 ` [Bug tree-optimization/111268] [11/12/13 " ricbal02 at gcc dot gnu.org
2024-05-08 12:46 ` cvs-commit at gcc dot gnu.org
2024-05-08 12:47 ` [Bug tree-optimization/111268] [11/12 " rguenth 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-111268-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).