public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108910] New: [13 Regression] Further ICE in aarch64_layout_arg
Date: Thu, 23 Feb 2023 20:56:02 +0000 [thread overview]
Message-ID: <bug-108910-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108910
Bug ID: 108910
Summary: [13 Regression] Further ICE in aarch64_layout_arg
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
extern void foo (float, float *, float *);
void
bar (void *p)
{
float *__attribute__((aligned (64))) q = __builtin_assume_aligned (p, 64);
foo (0.0f, q, q);
}
ICEs on aarch64-linux with -O2 likely since r13-5124 with:
during RTL pass: expand
woohoo.c: In function ‘bar’:
woohoo.c:7:3: internal compiler error: in aarch64_layout_arg, at
config/aarch64/aarch64.cc:7688
7 | foo (0.0f, q, q);
| ^~~~~~~~~~~~~~~~
0x12c4993 aarch64_layout_arg
../../gcc/config/aarch64/aarch64.cc:7688
0x12c527a aarch64_function_arg
../../gcc/config/aarch64/aarch64.cc:7868
0xa44efb initialize_argument_information
../../gcc/calls.cc:1499
I know trying to overalign a pointer type (rather than what it points to) is
very dumb,
but some real-world code (most likely just by mistake (but many)) does that:
https://github.com/darktable-org/darktable/blob/master/src/common/bspline.h#L178
next reply other threads:[~2023-02-23 20:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 20:56 jakub at gcc dot gnu.org [this message]
2023-02-23 20:56 ` [Bug target/108910] " jakub at gcc dot gnu.org
2023-02-23 21:01 ` pinskia at gcc dot gnu.org
2023-02-23 21:03 ` [Bug target/108910] [12/13 " pinskia at gcc dot gnu.org
2023-02-23 21:09 ` jakub at gcc dot gnu.org
2023-02-23 21:55 ` jakub at gcc dot gnu.org
2023-02-27 13:05 ` jakub at gcc dot gnu.org
2023-02-28 16:47 ` clyon at gcc dot gnu.org
2023-03-01 9:00 ` cvs-commit at gcc dot gnu.org
2023-03-01 9:04 ` jakub at gcc dot gnu.org
2023-03-10 15:10 ` clyon at gcc dot gnu.org
2023-03-10 15:14 ` jakub at gcc dot gnu.org
2023-03-10 16:09 ` jakub at gcc dot gnu.org
2023-03-19 5:29 ` cvs-commit at gcc dot gnu.org
2023-04-03 14:06 ` jakub at gcc dot gnu.org
2023-04-13 15:58 ` cvs-commit at gcc dot gnu.org
2023-04-13 15:58 ` [Bug target/108910] [12 " rsandifo at gcc dot gnu.org
2023-04-14 7:12 ` schwab@linux-m68k.org
2023-04-14 8:24 ` rguenth at gcc dot gnu.org
2023-04-14 18:19 ` ebotcazou at gcc dot gnu.org
2023-04-14 20:51 ` jason at gcc dot gnu.org
2023-04-17 13:41 ` cvs-commit at gcc dot gnu.org
2023-04-17 13:43 ` 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-108910-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).