public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109777] [14 regression] Compare-debug failure after recent changes Date: Mon, 08 May 2023 18:51:59 +0000 [thread overview] Message-ID: <bug-109777-4-nJkwSKRFyn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109777-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109777 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Component|middle-end |target Status|UNCONFIRMED |NEW Last reconfirmed| |2023-05-08 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The place where the first difference in IR (not withstanding the debug insns) is mach. Without -g, there is an forced_nop instruction being added: (insn:SI # # # 6 (set (reg:SI 3 R3 [177]) (ashift:SI (reg:SI 4 R4 [orig:87 x$0 ] [87]) (const_int 1 [0x1]))) "t.c":44:47# {*ashlsi3_insn} (nil)) (insn:SI # # # 6 (set (reg:SI 2 R2) (mem/c:SI (plus:SI (reg/f:SI 14 SP) (const_int 8 [0x8])) [4 %sfp+-4 S4 A32])) "t.c":44:47# {*movsi_insn} (nil)) (insn:QI # # # 6 (unspec [ (const_int 0 [0]) ] 12) "t.c":44:47# {forced_nop} (nil)) (insn:TI # # # 6 (set (reg:SI 6 R6) (reg:SI 19 I3 [165])) "t.c":44:53# {*movsi_insn} (nil)) While with -g, it is not there: (insn:TI # # # 6 (set (reg:SI 3 R3 [177]) (ashift:SI (reg:SI 4 R4 [orig:87 x$0 ] [87]) (const_int 1 [0x1]))) "t.c":44:47# {*ashlsi3_insn} (nil)) (debug_insn # # # 6 (var_location:SI D#14 (ior:SI (reg:SI 3 R3 [177]) (const_int 31 [0x1f])))# (nil)) (insn # # # 6 (set (reg:SI 2 R2) (mem/c:SI (plus:SI (reg/f:SI 14 SP) (const_int 8 [0x8])) [4 %sfp+-4 S4 A32])) "t.c":45:14# {*movsi_insn} (nil)) (insn:TI # # # 6 (set (reg:SI 6 R6) (reg:SI 19 I3 [165])) "t.c":44:53# {*movsi_insn} (nil))
next prev parent reply other threads:[~2023-05-08 18:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-08 18:20 [Bug tree-optimization/109777] New: " law at gcc dot gnu.org 2023-05-08 18:38 ` [Bug middle-end/109777] " pinskia at gcc dot gnu.org 2023-05-08 18:51 ` pinskia at gcc dot gnu.org [this message] 2023-05-08 19:05 ` [Bug target/109777] " pinskia at gcc dot gnu.org 2023-05-08 19:37 ` law at gcc dot gnu.org 2023-05-08 19:52 ` pinskia at gcc dot gnu.org 2024-05-07 7:40 ` [Bug target/109777] [14/15 " rguenth 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-109777-4-nJkwSKRFyn@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).