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/109483] Unoptimal uncprop with assembler flag output
Date: Wed, 12 Apr 2023 19:43:19 +0000 [thread overview]
Message-ID: <bug-109483-4-b9YElOI8AU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109483-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109483
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Uroš Bizjak from comment #4)
> Even the above is not optimal. I'd expect:
>
> ...
> .L8:
> #APP
> # 6 "t.c" 1
> int3
> # 0 "" 2
> #NO_APP
> je .L2
> xorl %eax, %eax
> ret
IF-CASE-2 found, start 3, else 5
verify found no changes in insn with uid = 15.
changing bb of uid 4
from 5 to 3
deleting block 5
Conversion succeeded on pass 1.
Adding -fno-if-conversion gets what you want too. But I am not 100% sure if it
is "better".
prev parent reply other threads:[~2023-04-12 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 8:54 [Bug rtl-optimization/109483] New: Unoptimal jump threading " ubizjak at gmail dot com
2023-04-12 8:59 ` [Bug middle-end/109483] " pinskia at gcc dot gnu.org
2023-04-12 10:47 ` [Bug tree-optimization/109483] Unoptimal uncprop " rguenth at gcc dot gnu.org
2023-04-12 10:48 ` rguenth at gcc dot gnu.org
2023-04-12 14:40 ` ubizjak at gmail dot com
2023-04-12 19:43 ` pinskia at gcc dot gnu.org [this message]
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-109483-4-b9YElOI8AU@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: link
Be 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).