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/98998] [11 Regression] ICE in change_address_1, at emit-rtl.c:2275 since r11-3427
Date: Fri, 19 Feb 2021 12:09:37 +0000 [thread overview]
Message-ID: <bug-98998-4-D2gDyN0BYB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98998-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98998
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:1a132c4d7cdb22cbab85b8596418daa2c3157812
commit r11-7295-g1a132c4d7cdb22cbab85b8596418daa2c3157812
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Feb 19 13:05:47 2021 +0100
arm: Fix ICE with -fstack-protector -mpure-code [PR98998]
The vla15.C testcase ICEs with
-mcpu=cortex-m1 -mpure-code -fstack-protector -mthumb
as what force_const_mem returns (a SYMBOL_REF) is not a valid
memory address.
Previously the code was moving the address of the force_const_mem
into a register rather than the content of that MEM, so that instruction
must have been supported and loading from a MEM with a single REG base
ought
to be valid too.
2021-02-19 Jakub Jelinek <jakub@redhat.com>
PR target/98998
* config/arm/arm.md (*stack_protect_combined_set_insn,
*stack_protect_combined_test_insn): If force_const_mem result
is not valid general operand, force its address into the
destination
register first.
* gcc.target/arm/pure-code/pr98998.c: New test.
next prev parent reply other threads:[~2021-02-19 12:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 9:14 [Bug target/98998] New: ICE in change_address_1, at emit-rtl.c:2275 marxin at gcc dot gnu.org
2021-02-09 17:20 ` [Bug target/98998] [11 Regression] ICE in change_address_1, at emit-rtl.c:2275 since r11-3427 jakub at gcc dot gnu.org
2021-02-09 17:20 ` jakub at gcc dot gnu.org
2021-02-11 11:30 ` jakub at gcc dot gnu.org
2021-02-11 11:54 ` jakub at gcc dot gnu.org
2021-02-11 12:17 ` rsandifo at gcc dot gnu.org
2021-02-11 12:20 ` jakub at gcc dot gnu.org
2021-02-11 14:36 ` clyon at gcc dot gnu.org
2021-02-16 15:00 ` jakub at gcc dot gnu.org
2021-02-19 12:09 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-19 12:10 ` jakub 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-98998-4-D2gDyN0BYB@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).