public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "avi at scylladb dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/107772] New: [missed optimization] function prologue generated even though it's only needed in an unlikely path Date: Sun, 20 Nov 2022 18:48:15 +0000 [thread overview] Message-ID: <bug-107772-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107772 Bug ID: 107772 Summary: [missed optimization] function prologue generated even though it's only needed in an unlikely path Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: avi at scylladb dot com Target Milestone: --- Consider int g(int); void f(int* b, int* e) { while (b != e) { if (__builtin_expect(*b != 0, false)) [[unlikely]] { *b = g(*b); } ++b; } } If we believe the __builtin_expect and/or unlikely annotations (had both for extra safety), the loop usually does nothing. So we would expect any register saving and restoring to be pushed to the unlikely section. Yet (-O3): f(int*, int*): cmp rdi, rsi je .L10 push rbp mov rbp, rsi push rbx mov rbx, rdi sub rsp, 8 .L4: mov edi, DWORD PTR [rbx] test edi, edi jne .L14 .L3: add rbx, 4 cmp rbp, rbx jne .L4 add rsp, 8 pop rbx pop rbp ret .L14: call g(int) mov DWORD PTR [rbx], eax jmp .L3 .L10: ret I count 8 instructions that could/should have been pushed to .L14.
next reply other threads:[~2022-11-20 18:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-20 18:48 avi at scylladb dot com [this message] 2022-11-20 19:23 ` [Bug rtl-optimization/107772] " pinskia at gcc dot gnu.org 2022-11-28 18:08 ` avi at scylladb dot com 2022-11-28 18:13 ` pinskia at gcc dot gnu.org 2022-11-28 18:34 ` amonakov at gcc dot gnu.org 2022-11-28 20:32 ` avi at scylladb 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-107772-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).