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/109866] New: Sometimes using sub/test instead just test
Date: Mon, 15 May 2023 18:44:19 +0000	[thread overview]
Message-ID: <bug-109866-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109866

            Bug ID: 109866
           Summary: Sometimes using sub/test instead just test
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P3
         Component: rtl-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

Take:
```
int g(void); int h(void); int t(void);
int f(int a, int b)
{
  int c = a - b;
  if(c == 0)
    return g();
  if (c > 0)
    return h();
  return t();
}
```
This is reduced from bzip2 in spec 2006, though I am not so sure any more.
On x86_64 GCC produces:
```
        subl    %esi, %edi
        testl   %edi, %edi
        je      .L5
        jle     .L3
        jmp     h()
.L3:
        jmp     t()
.L5:
        jmp     g()
```
But GCC should produce (likes clang/LLVM does):
```
        cmpl    %esi, %edi
        je      .L5
        jle     .L3
        jmp     h()
.L3:
        jmp     t()
.L5:
        jmp     g()
```

Note a similar thing happens with aarch64 target too.

             reply	other threads:[~2023-05-15 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 18:44 pinskia at gcc dot gnu.org [this message]
2023-05-16  8:07 ` [Bug rtl-optimization/109866] " ubizjak at gmail dot com
2023-05-16  8:19 ` ubizjak at gmail dot com
2023-05-16 10:24 ` pinskia at gcc dot gnu.org
2023-05-16 15:50 ` [Bug tree-optimization/109866] " pinskia at gcc dot gnu.org
2023-05-17  6:56 ` 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-109866-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: 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).