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 rtl-optimization/105653] [10/11/12/13 Regression] '-fcompare-debug' failure w/ -O2 Date: Thu, 27 Oct 2022 00:42:02 +0000 [thread overview] Message-ID: <bug-105653-4-bejAd2z0Um@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105653-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105653 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2022-10-27 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- IRA adds the REG_EQUIV note even for both with/without -g. But it was removed in peephole2 for -g case. In the -g case we get the following extra output in -g for peephole2 starting with: df_worklist_dataflow_doublequeue: n_basic_blocks 8 n_edges 10 count 9 ( 1.1) .... DCE: Deleting insn 15 deleting insn with uid = 15. ... insn 15 was: (insn:TI 15 13 16 2 (set (reg/f:DI 1 x1 [101]) (plus:DI (reg/f:DI 0 x0 [orig:99 thisD.4083 ] [99]) (const_int 8 [0x8]))) "/app/example.cpp":9:25 discrim 1 141 {*adddi3_aarch64} (expr_list:REG_UNUSED (reg/f:DI 1 x1 [101]) (nil))) in sched_fusion. But in the -g0 case, it was not removed inside peephole2. Someone who understands DF DCE better should look into this on why it was not removed inside peephole2 without -g. The instruction without -g: (insn:TI 8 3 9 2 (set (reg/f:DI 1 x1 [101]) (plus:DI (reg/f:DI 0 x0 [orig:99 this ] [99]) (const_int 8 [0x8]))) "/app/example.cpp":9:25 discrim 1 141 {*adddi3_aarch64} (expr_list:REG_UNUSED (reg/f:DI 1 x1 [101]) (nil))) Which looks exactly the same even.
next prev parent reply other threads:[~2022-10-27 0:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-19 6:18 [Bug debug/105653] New: " asolokha at gmx dot com 2022-05-19 6:21 ` [Bug debug/105653] " rguenth at gcc dot gnu.org 2022-06-28 10:49 ` jakub at gcc dot gnu.org 2022-08-03 3:03 ` [Bug rtl-optimization/105653] " asolokha at gmx dot com 2022-10-27 0:42 ` pinskia at gcc dot gnu.org [this message] 2022-12-20 13:46 ` rguenth at gcc dot gnu.org 2023-07-07 10:43 ` [Bug rtl-optimization/105653] [11/12/13/14 " 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-105653-4-bejAd2z0Um@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).