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 rtl-optimization/105041] '-fcompare-debug' failure w/ -mcpu=power6 -O2 -fharden-compares -frename-registers Date: Tue, 14 Jun 2022 17:39:58 +0000 [thread overview] Message-ID: <bug-105041-4-dN7whISMwQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105041-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105041 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Segher Boessenkool <segher@gcc.gnu.org>: https://gcc.gnu.org/g:3e16b4359e86b36676ed01219e6deafa95f3c16b commit r13-1092-g3e16b4359e86b36676ed01219e6deafa95f3c16b Author: Surya Kumari Jangala <jskumari@linux.vnet.ibm.com> Date: Fri Jun 10 19:52:57 2022 +0530 regrename: Fix -fcompare-debug issue in check_new_reg_p [PR105041] In check_new_reg_p, the nregs of a du chain is computed by obtaining the MODE of the first element in the chain, and then calling hard_regno_nregs() with the MODE. But the first element of the chain can be a DEBUG_INSN whose mode need not be the same as the rest of the elements in the du chain. This was resulting in fcompare-debug failure as check_new_reg_p was returning a different result with -g for the same candidate register. We can instead obtain nregs from the du chain itself. 2022-06-10 Surya Kumari Jangala <jskumari@linux.ibm.com> gcc/ PR rtl-optimization/105041 * regrename.cc (check_new_reg_p): Use nregs value from du chain. gcc/testsuite/ PR rtl-optimization/105041 * gcc.target/powerpc/pr105041.c: New test.
next prev parent reply other threads:[~2022-06-14 17:39 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-24 7:38 [Bug debug/105041] New: " asolokha at gmx dot com 2022-03-24 9:02 ` [Bug debug/105041] " rguenth at gcc dot gnu.org 2022-03-29 21:58 ` bergner at gcc dot gnu.org 2022-03-29 22:13 ` bergner at gcc dot gnu.org 2022-04-01 13:33 ` bergner at gcc dot gnu.org 2022-04-05 22:46 ` segher at gcc dot gnu.org 2022-04-07 5:30 ` jskumari at gcc dot gnu.org 2022-06-14 17:39 ` cvs-commit at gcc dot gnu.org [this message] 2022-06-15 5:25 ` [Bug rtl-optimization/105041] " jskumari at gcc dot gnu.org 2022-06-16 5:08 ` jskumari at gcc dot gnu.org 2022-07-14 14:07 ` cvs-commit at gcc dot gnu.org 2022-07-21 6:38 ` cvs-commit at gcc dot gnu.org 2022-07-22 9:53 ` cvs-commit at gcc dot gnu.org 2022-07-23 6:55 ` asolokha at gmx dot com 2022-07-23 16:28 ` bergner 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-105041-4-dN7whISMwQ@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).