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 tree-optimization/108007] wrong code at -Os and above with "-fno-dce -fno-tree-dce" on x86_64-linux-gnu Date: Wed, 07 Dec 2022 16:45:19 +0000 [thread overview] Message-ID: <bug-108007-4-LP7R8qXQIZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108007-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108007 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- #(insn:TI 36 66 40 8 (set (reg:CCGC 17 flags) # (compare:CCGC (mem:SI (const_int 0 [0]) [1 *removed_return.17_12(D)+0 S4 A32]) # (reg:SI 1 dx [orig:83 b.0_5 ] [83]))) "/app/example.cpp":20:13 11 {*cmpsi_1} # (expr_list:REG_UNUSED (reg:CCGC 17 flags) # (nil))) cmpl %edx, 0 # 36 [c=8 l=7] *cmpsi_1/0
next prev parent reply other threads:[~2022-12-07 16:45 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-07 12:44 [Bug tree-optimization/108007] New: " zhendong.su at inf dot ethz.ch 2022-12-07 16:45 ` pinskia at gcc dot gnu.org [this message] 2022-12-07 16:54 ` [Bug ipa/108007] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-12-07 16:59 ` pinskia at gcc dot gnu.org 2022-12-07 17:00 ` pinskia at gcc dot gnu.org 2022-12-08 9:50 ` marxin at gcc dot gnu.org 2022-12-21 11:41 ` rguenth at gcc dot gnu.org 2023-04-03 14:32 ` jakub at gcc dot gnu.org 2023-04-03 14:35 ` jakub at gcc dot gnu.org 2023-05-12 12:57 ` [Bug ipa/108007] [10/11/12/13/14 " jamborm at gcc dot gnu.org 2023-07-07 10:44 ` [Bug ipa/108007] [11/12/13/14 " rguenth at gcc dot gnu.org 2023-09-20 14:10 ` jamborm at gcc dot gnu.org 2023-09-21 2:15 ` pinskia at gcc dot gnu.org 2023-09-21 2:17 ` pinskia at gcc dot gnu.org 2023-09-21 2:19 ` pinskia at gcc dot gnu.org 2023-09-22 17:30 ` pinskia at gcc dot gnu.org 2023-10-03 16:53 ` cvs-commit at gcc dot gnu.org 2023-10-03 17:18 ` jamborm at gcc dot gnu.org 2023-10-05 12:13 ` jamborm at gcc dot gnu.org 2024-01-11 1:05 ` [Bug ipa/108007] [11/12/13/14 Regression] wrong code at -Os and above with "-fno-dce -fno-tree-dce" on x86_64-linux-gnu since r10-3311-gff6686d2e5f797 pinskia at gcc dot gnu.org 2024-01-16 12:44 ` jamborm at gcc dot gnu.org 2024-01-24 18:14 ` cvs-commit at gcc dot gnu.org 2024-01-24 19:09 ` jamborm at gcc dot gnu.org 2024-04-08 15:51 ` [Bug ipa/108007] [11/12/13 " cvs-commit at gcc dot gnu.org 2024-05-15 13:46 ` [Bug ipa/108007] [11/12 " 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-108007-4-LP7R8qXQIZ@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).