public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/108910] [12/13 Regression] Further ICE in aarch64_layout_arg
Date: Tue, 28 Feb 2023 16:47:54 +0000 [thread overview]
Message-ID: <bug-108910-4-izJZe7yH05@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108910-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108910
Christophe Lyon <clyon at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu.org
--- Comment #6 from Christophe Lyon <clyon at gcc dot gnu.org> ---
I can see that aarch64_function_arg_alignment has:
if (!AGGREGATE_TYPE_P (type))
return TYPE_ALIGN (TYPE_MAIN_VARIANT (type));
which returns 512 with the testcase from comment #0
type is (TYPE_MAIN_VARIANT(type) is the same):
<pointer_type 0x7ffff74f7bd0
type <real_type 0x7ffff76222a0 float SF
size <integer_cst 0x7ffff761e060 constant 32>
unit-size <integer_cst 0x7ffff761e078 constant 4>
align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff76222a0 precision:32
pointer_to_this <pointer_type 0x7ffff7622888>>
sizes-gimplified public unsigned DI
size <integer_cst 0x7ffff7602e10 type <integer_type 0x7ffff761a0a8
bitsizetype> constant 64>
unit-size <integer_cst 0x7ffff7602e28 type <integer_type 0x7ffff761a000
sizetype> constant 8>
user align:512 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff7622888
attributes <tree_list 0x7ffff74fb280
purpose <identifier_node 0x7ffff74fc8c0 aligned>
value <tree_list 0x7ffff74fb208
value <integer_cst 0x7ffff7769b58 constant 64>>>>
next prev parent reply other threads:[~2023-02-28 16:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 20:56 [Bug target/108910] New: [13 " jakub at gcc dot gnu.org
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 [this message]
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-izJZe7yH05@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).