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/109862] New: IV-OPTs could use int but still uses smaller sized for IV
Date: Mon, 15 May 2023 16:24:54 +0000	[thread overview]
Message-ID: <bug-109862-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109862
           Summary: IV-OPTs could use int but still uses smaller sized for
                    IV
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---
            Target: aarch64, riscv32, riscv64

Take:
```
int f(char a)
{
        unsigned char t;
        unsigned short t1 = a;
        for(t = 0; t < 8; t ++)
        {
                t1 >>=1;
                t1 += a;
        }
        return t1;
}
int f1(char a)
{
        unsigned int t;
        unsigned short t1 = a;
        for(t = 0; t < 8; t ++)
        {
                t1 >>=1;
                t1 += a;
        }
        return t1;
}

```
f1 produces better code as there is no extra zero-extend (anding) inside the
loop for the IV of t.

Note this shows up in coremarks in the crc functions (if not unrolling).

             reply	other threads:[~2023-05-15 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 16:24 pinskia at gcc dot gnu.org [this message]
2023-05-15 16:25 ` [Bug tree-optimization/109862] " pinskia at gcc dot gnu.org
2023-05-17  6:46 ` 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-109862-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).