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 target/109661] [13 Regression] ICE in aarch64_function_arg_alignment when building erlang
Date: Thu, 11 May 2023 11:36:39 +0000 [thread overview]
Message-ID: <bug-109661-4-ADqzpx7VmK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109661-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109661
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Richard Sandiford
<rsandifo@gcc.gnu.org>:
https://gcc.gnu.org/g:891cdd3b935e3ee9f1b2ecf7390801c534d39a90
commit r13-7318-g891cdd3b935e3ee9f1b2ecf7390801c534d39a90
Author: Richard Sandiford <richard.sandiford@arm.com>
Date: Thu May 11 12:36:26 2023 +0100
aarch64: Remove alignment assertions [PR109661]
The trunk patch for this PR corrected the ABI for enums that have
a defined underlying type. We shouldn't change the ABI on the branches
though, so this patch just removes the assertions that highlighed
the problem.
I think the same approach makes sense longer-term: keep the assertions
at maximum strength in trunk, and in any new branches that get cut.
Then, if the assertions trip an ABI problem, fix the problem in trunk
and remove the assertions from active branches.
The tests are the same as for the trunk version, but with all Wpsabi
message and expected output checks removed.
gcc/
PR target/109661
* config/aarch64/aarch64.cc (aarch64_function_arg_alignment):
Remove
assertion.
(aarch64_layout_arg): Likewise.
gcc/testsuite/
PR target/109661
* g++.target/aarch64/pr109661-1.C: New test.
* g++.target/aarch64/pr109661-2.C: Likewise.
* g++.target/aarch64/pr109661-3.C: Likewise.
* g++.target/aarch64/pr109661-4.C: Likewise.
* gcc.target/aarch64/pr109661-1.c: Likewise.
next prev parent reply other threads:[~2023-05-11 11:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 8:18 [Bug target/109661] New: [13/14 " jakub at gcc dot gnu.org
2023-04-28 8:18 ` [Bug target/109661] " jakub at gcc dot gnu.org
2023-04-28 8:19 ` jakub at gcc dot gnu.org
2023-04-28 8:28 ` jakub at gcc dot gnu.org
2023-04-28 8:44 ` jakub at gcc dot gnu.org
2023-04-28 8:56 ` rsandifo at gcc dot gnu.org
2023-04-28 8:56 ` rsandifo at gcc dot gnu.org
2023-05-02 11:29 ` jakub at gcc dot gnu.org
2023-05-02 11:50 ` rsandifo at gcc dot gnu.org
2023-05-03 16:44 ` cvs-commit at gcc dot gnu.org
2023-05-03 16:44 ` cvs-commit at gcc dot gnu.org
2023-05-03 16:49 ` [Bug target/109661] [13 " rsandifo at gcc dot gnu.org
2023-05-09 12:18 ` sjames at gcc dot gnu.org
2023-05-11 11:36 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-19 11:24 ` 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-109661-4-ADqzpx7VmK@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).