public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "theodort at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103359] New: [12 Regression] Dead Code Elimination Regression at -O3 (trunk vs 11.2.0) Date: Mon, 22 Nov 2021 15:34:16 +0000 [thread overview] Message-ID: <bug-103359-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103359 Bug ID: 103359 Summary: [12 Regression] Dead Code Elimination Regression at -O3 (trunk vs 11.2.0) Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: theodort at inf dot ethz.ch Target Milestone: --- cat case.c void foo(); static char a, c; static int d, e; static short b(short f, short g) { return f * g; } int main() { short h = 4; for (; d;) if (h) if(e) { if (!b(a & 1 | h, 3)) c = 0; h = 1; } if (c) foo(); } trunk cannot eliminate the call to foo but 11.2.0 can: gcc-11.2.0 -O3 -S -o /dev/stdout case.c main: .LFB1: .cfi_startproc xorl %eax, %eax ret .cfi_endproc gcc-trunk -O3 -S -o /dev/stdout case.c main: .LFB1: .cfi_startproc cmpb $0, c(%rip) jne .L8 xorl %eax, %eax ret .L8: pushq %rax .cfi_def_cfa_offset 16 xorl %eax, %eax call foo xorl %eax, %eax popq %rdx .cfi_def_cfa_offset 8 ret .cfi_endproc gcc-trunk -v Using built-in specs. Target: x86_64-pc-linux-gnu Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 12.0.0 20211122 (experimental) (GCC) Started with https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=408579c9c9b8fee20e1d8114489ce2b93872767c
next reply other threads:[~2021-11-22 15:34 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-22 15:34 theodort at inf dot ethz.ch [this message] 2021-11-22 22:04 ` [Bug tree-optimization/103359] " pinskia at gcc dot gnu.org 2021-11-22 22:23 ` pinskia at gcc dot gnu.org 2021-11-23 7:30 ` rguenth at gcc dot gnu.org 2021-11-23 10:11 ` rguenth at gcc dot gnu.org 2021-11-23 11:16 ` rguenth at gcc dot gnu.org 2021-11-23 11:36 ` rguenth at gcc dot gnu.org 2021-11-23 11:37 ` rguenth at gcc dot gnu.org 2021-11-23 13:09 ` aldyh at gcc dot gnu.org 2021-11-23 13:13 ` aldyh at gcc dot gnu.org 2021-11-23 16:03 ` amacleod at redhat dot com 2021-11-25 13:44 ` cvs-commit at gcc dot gnu.org 2021-11-25 13:45 ` amacleod at redhat dot com
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-103359-4@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).