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/94538] [9/10/11 Regression] ICE: in extract_constrain_insn_cached, at recog.c:2223 (insn does not satisfy its constraints) with -mcpu=cortex-m23 -mslow-flash-data Date: Thu, 27 Aug 2020 11:12:24 +0000 [thread overview] Message-ID: <bug-94538-4-CKORLDtM31@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94538-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94538 --- Comment #22 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Christophe Lyon <clyon@gcc.gnu.org>: https://gcc.gnu.org/g:967a5f8e585a5d499870903849c0fa06c326547a commit r9-8835-g967a5f8e585a5d499870903849c0fa06c326547a Author: Christophe Lyon <christophe.lyon@linaro.org> Date: Wed Aug 19 09:02:21 2020 +0000 arm: Fix -mpure-code support/-mslow-flash-data for armv8-m.base [PR94538] armv8-m.base (cortex-m23) has the movt instruction, so we need to disable the define_split to generate a constant in this case, otherwise we get incorrect insn constraints as described in PR94538. We also need to fix the pure-code alternative for thumb1_movsi_insn because the assembler complains with instructions like movs r0, #:upper8_15:1234 (Internal error in md_apply_fix) We now generate movs r0, 4 instead. 2020-08-24 Christophe Lyon <christophe.lyon@linaro.org> PR target/94538 gcc/ * config/arm/thumb1.md: Disable set-constant splitter when TARGET_HAVE_MOVT. (thumb1_movsi_insn): Fix -mpure-code alternative. PR target/94538 gcc/testsuite/ * gcc.target/arm/pure-code/pr94538-1.c: New test. * gcc.target/arm/pure-code/pr94538-2.c: New test. (cherry picked from commit 259d072067997ab8f55afcf735c91b6740fd0425)
next prev parent reply other threads:[~2020-08-27 11:12 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-09 11:02 [Bug target/94538] New: [9/10 " zsojka at seznam dot cz 2020-04-09 13:38 ` [Bug target/94538] " wilco at gcc dot gnu.org 2020-04-09 16:35 ` [Bug target/94538] [10 " wilco at gcc dot gnu.org 2020-04-09 17:46 ` zsojka at seznam dot cz 2020-04-09 18:08 ` wilco at gcc dot gnu.org 2020-04-10 23:42 ` cvs-commit at gcc dot gnu.org 2020-04-10 23:51 ` iains at gcc dot gnu.org 2020-04-14 11:28 ` wilco at gcc dot gnu.org 2020-04-14 12:16 ` clyon at gcc dot gnu.org 2020-04-14 12:54 ` zsojka at seznam dot cz 2020-04-14 14:42 ` wilco at gcc dot gnu.org 2020-04-14 17:08 ` clyon at gcc dot gnu.org 2020-04-16 15:40 ` clyon at gcc dot gnu.org 2020-04-16 16:44 ` wilco at gcc dot gnu.org 2020-04-16 17:10 ` wilco at gcc dot gnu.org 2020-04-16 19:41 ` clyon at gcc dot gnu.org 2020-04-17 10:23 ` wilco at gcc dot gnu.org 2020-04-30 7:27 ` [Bug target/94538] [9/10 " rguenth at gcc dot gnu.org 2020-04-30 9:44 ` clyon at gcc dot gnu.org 2020-04-30 12:28 ` wilco at gcc dot gnu.org 2020-08-24 9:09 ` [Bug target/94538] [9/10/11 " cvs-commit at gcc dot gnu.org 2020-08-24 13:32 ` clyon at gcc dot gnu.org 2020-08-27 11:12 ` cvs-commit at gcc dot gnu.org [this message] 2020-08-27 11:18 ` cvs-commit at gcc dot gnu.org 2020-08-27 11:19 ` clyon 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-94538-4-CKORLDtM31@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: linkBe 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).