public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/108573] [13 Regression] '-fcompare-debug' failure (length) at -O2 Date: Tue, 31 Jan 2023 16:38:25 +0000 [thread overview] Message-ID: <bug-108573-4-a5JxYIc3mr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108573-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108573 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC| |jakub at gcc dot gnu.org Last reconfirmed| |2023-01-31 --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> --- This diverges during REE: Trying to eliminate extension: -(insn 10023 10022 10027 2 (set (reg:DI 15 a5 [orig:139 _6 ] [139]) +(insn 10023 9 10027 2 (set (reg:DI 15 a5 [orig:139 _6 ] [139]) (sign_extend:DI (reg:SI 10 a0 [160]))) "pr108573.c":11:5 116 {extendsidi2} (nil)) -Tentatively merged extension with definition (copy needed): -(insn 10022 10018 10023 2 (set (reg:DI 15 a5) - (sign_extend:DI (umod:SI (reg:SI 10 a0 [157]) - (reg:SI 14 a4 [orig:162 g ] [162])))) "pr108573.c":11:5 -1 - (nil)) -deferring rescan insn with uid = 10022. -All merges were successful. -Eliminated the extension. -deferring rescan insn with uid = 10055. -deferring deletion of insn with uid = 10023. -Elimination opportunities = 2 realized = 1 +Elimination opportunities = 2 realized = 0 starting the processing of deferred insns -rescanning insn with uid = 10022. -rescanning insn with uid = 10055. ending the processing of deferred insns
next prev parent reply other threads:[~2023-01-31 16:38 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-27 16:38 [Bug debug/108573] New: " zsojka at seznam dot cz 2023-01-30 7:58 ` [Bug debug/108573] " rguenth at gcc dot gnu.org 2023-01-31 16:38 ` jakub at gcc dot gnu.org [this message] 2023-01-31 17:05 ` jakub at gcc dot gnu.org 2023-01-31 17:46 ` jakub at gcc dot gnu.org 2023-02-01 11:53 ` cvs-commit at gcc dot gnu.org 2023-02-01 11:54 ` jakub at gcc dot gnu.org 2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org 2023-05-02 20:14 ` cvs-commit at gcc dot gnu.org 2023-05-03 15:21 ` 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-108573-4-a5JxYIc3mr@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).