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/99725] arm: ICE in dwarf2out_frame_debug_adjust_cfa with -mcmse
Date: Tue, 11 May 2021 12:12:19 +0000 [thread overview]
Message-ID: <bug-99725-4-4kwc1b3NMg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99725-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99725
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Alex Coplan <acoplan@gcc.gnu.org>:
https://gcc.gnu.org/g:2ac1f0eb3887335b7a7e845812956fa436e72a91
commit r12-715-g2ac1f0eb3887335b7a7e845812956fa436e72a91
Author: Alex Coplan <alex.coplan@arm.com>
Date: Tue May 11 13:11:09 2021 +0100
arm: Avoid emitting bogus CFA adjusts for CMSE nonsecure calls [PR99725]
The PR shows us attaching REG_CFA_ADJUST_CFA notes to stack pointer
adjustments emitted in cmse_nonsecure_call_inline_register_clear (when
-march=armv8.1-m.main). However, the stack pointer is not guaranteed to
be the CFA reg. If we're at -O0 or we have -fno-omit-frame-pointer, then
the frame pointer will be used as the CFA reg, and these notes on the sp
adjustments will lead to ICEs in dwarf2out_frame_debug_adjust_cfa.
This patch avoids emitting these notes if the current function has a
frame pointer.
gcc/ChangeLog:
PR target/99725
* config/arm/arm.c (cmse_nonsecure_call_inline_register_clear):
Avoid emitting CFA adjusts on the sp if we have the fp.
gcc/testsuite/ChangeLog:
PR target/99725
* gcc.target/arm/cmse/pr99725.c: New test.
next prev parent reply other threads:[~2021-05-11 12:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 10:45 [Bug target/99725] New: " acoplan at gcc dot gnu.org
2021-04-30 9:29 ` [Bug target/99725] " acoplan at gcc dot gnu.org
2021-05-11 12:12 ` cvs-commit at gcc dot gnu.org [this message]
2021-05-11 12:13 ` acoplan at gcc dot gnu.org
2021-05-27 9:42 ` cvs-commit at gcc dot gnu.org
2021-06-01 16:22 ` cvs-commit at gcc dot gnu.org
2021-06-01 16:29 ` acoplan at gcc dot gnu.org
2021-09-17 6:43 ` pinskia 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-99725-4-4kwc1b3NMg@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).