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/111528] aarch64: Test gfortran.dg/pr80494.f90 fails with -fstack-protector-strong with gcc-13 since r13-7813-gb96e66fd4ef3e3 Date: Wed, 18 Oct 2023 17:45:10 +0000 [thread overview] Message-ID: <bug-111528-4-0cGHtt6K7A@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111528-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111528 --- Comment #5 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:f5e56c5857cc6b704446c3666213468d25f6dcb2 commit r13-7961-gf5e56c5857cc6b704446c3666213468d25f6dcb2 Author: Richard Sandiford <richard.sandiford@arm.com> Date: Wed Oct 18 18:44:57 2023 +0100 lra: Avoid unfolded plus-0 While backporting another patch to an earlier release, I hit a situation in which lra_eliminate_regs_1 would eliminate an address to: (plus (reg:P R) (const_int 0)) This address compared not-equal to plain: (reg:P R) which caused an ICE in a later peephole2. (The ICE showed up in gfortran.fortran-torture/compile/pr80464.f90 on the branch but seems to be latent on trunk.) These unfolded PLUSes shouldn't occur in the insn stream, and later code in the same function tried to avoid them. gcc/ PR target/111528 * lra-eliminations.cc (lra_eliminate_regs_1): Use simplify_gen_binary rather than gen_rtx_PLUS. (cherry picked from commit 10d59b802a7db9ae908291fb20627c1493cfa26c)
next prev parent reply other threads:[~2023-10-18 17:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-21 19:53 [Bug target/111528] New: aarch64: Test gfortran.dg/pr80494.f90 fails with -fstack-protector-strong with gcc-13 mpolacek at gcc dot gnu.org 2023-09-21 19:55 ` [Bug target/111528] " pinskia at gcc dot gnu.org 2023-09-21 20:00 ` mpolacek at gcc dot gnu.org 2023-09-24 21:26 ` [Bug target/111528] aarch64: Test gfortran.dg/pr80494.f90 fails with -fstack-protector-strong with gcc-13 since r13-7813-gb96e66fd4ef3e3 rsandifo at gcc dot gnu.org 2023-10-11 9:40 ` jakub at gcc dot gnu.org 2023-10-18 17:45 ` cvs-commit at gcc dot gnu.org [this message] 2023-10-19 9:49 ` cvs-commit at gcc dot gnu.org 2023-10-19 22:21 ` 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-111528-4-0cGHtt6K7A@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).