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 debug/105627] -fcompare-debug failure at -Og for powerpc64le-unknown-linux-gnu Date: Tue, 24 May 2022 06:08:58 +0000 [thread overview] Message-ID: <bug-105627-4-pZs2Mtz50o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105627-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105627 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>: https://gcc.gnu.org/g:149d04ccbb908b3a251485b43faf204752942b9f commit r13-720-g149d04ccbb908b3a251485b43faf204752942b9f Author: Kewen Lin <linkw@linux.ibm.com> Date: Tue May 24 01:00:22 2022 -0500 rs6000: Skip debug insns for union [PR105627] As PR105627 exposes, pass analyze_swaps should skip debug insn when doing unionfind_union. One debug insn can use several pseudos, if we take debug insn into account, we can union those insns defining them and generate some unexpected unions. Based on the assumption that it's impossible to have one pseudo which is defined by one debug insn but is used by one nondebug insn, we just asserts debug insn never shows up in function union_defs. PR target/105627 gcc/ChangeLog: * config/rs6000/rs6000-p8swap.cc (union_defs): Assert def_insn can't be a debug insn. (union_uses): Skip debug use_insn. gcc/testsuite/ChangeLog: * gcc.target/powerpc/pr105627.c: New test.
next prev parent reply other threads:[~2022-05-24 6:08 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-17 12:19 [Bug debug/105627] New: " zsojka at seznam dot cz 2022-05-18 14:53 ` [Bug debug/105627] " jakub at gcc dot gnu.org 2022-05-19 7:28 ` linkw at gcc dot gnu.org 2022-05-24 6:08 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-24 6:22 ` linkw at gcc dot gnu.org 2022-10-27 2:25 ` [Bug target/105627] " pinskia 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-105627-4-pZs2Mtz50o@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).