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/110484] Spec2017 541 after adding the '-flto-fomit-frame-pointer' optimization, after optimizing the rnreg, directly replaced other registers with the $r22 register, so that the value of the $r22 register was destroyed without being saved. Date: Fri, 01 Sep 2023 02:04:44 +0000 [thread overview] Message-ID: <bug-110484-4-zp52BkQsiP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110484-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110484 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by LuluCheng <chenglulu@gcc.gnu.org>: https://gcc.gnu.org/g:1967f21d000e09d3d3190317af7923b578ce02b1 commit r14-3605-g1967f21d000e09d3d3190317af7923b578ce02b1 Author: Lulu Cheng <chenglulu@loongson.cn> Date: Thu Jun 29 19:30:59 2023 +0800 LoongArch: Fix bug in loongarch_emit_stack_tie [PR110484]. Which may result in implicit references to $fp when frame_pointer_needed is false, causing regs_ever_live[$fp] to be true when $fp is not explicitly used, resulting in $fp being used as the target replacement register in the rnreg pass. The bug originates from SPEC2017 541.leela_r(-flto). gcc/ChangeLog: PR target/110484 * config/loongarch/loongarch.cc (loongarch_emit_stack_tie): Use the frame_pointer_needed to determine whether to use the $fp register. Co-authored-by: Guo Jie <guojie@loongson.cn>
next prev parent reply other threads:[~2023-09-01 2:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-29 11:25 [Bug c++/110484] New: " chenglulu at loongson dot cn 2023-06-29 12:07 ` [Bug c++/110484] " chenglulu at loongson dot cn 2023-06-29 15:33 ` xry111 at gcc dot gnu.org 2023-09-01 2:04 ` cvs-commit at gcc dot gnu.org [this message] 2023-09-01 2:12 ` [Bug target/110484] " chenglulu at loongson dot cn 2023-09-01 2:43 ` cvs-commit at gcc dot gnu.org 2023-09-01 3:23 ` cvs-commit 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-110484-4-zp52BkQsiP@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).