From: Richard Biener <richard.guenther@gmail.com>
To: Roger Sayle <roger@nextmovesoftware.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Optimize (X<<C)+(Y<<C) as (X+Y)<<C for signed addition.
Date: Wed, 14 Sep 2022 10:28:30 +0200 [thread overview]
Message-ID: <CAFiYyc2zjStxUqR=JO6Tpgfx0Rn6pitxXZPiWHxUzc7JW5N8LQ@mail.gmail.com> (raw)
In-Reply-To: <002d01d8c79f$dc5fe830$951fb890$@nextmovesoftware.com>
On Tue, Sep 13, 2022 at 8:37 PM Roger Sayle <roger@nextmovesoftware.com> wrote:
>
>
> This patch tweaks the match.pd transformation previously added to fold
> (X<<C)+(Y<<C) as (X+Y)<<C that was previously restricted to unsigned
> (wrapping) types, to also allow signed integer types provided that they
> don't trap and the overflow needn't be preserved for sanitization.
> i.e. this should now apply (by default) for "int x,y;", but is disabled
> with -ftrapv.
>
> This unsigned transformation has baked on mainline without problems, so it's
> time to turn up the heat... LLVM, icc and MSVC perform this optimization.
>
>
> This patch has been tested on x86_64-pc-linux-gnu with make bootstrap and
> make -k check, both with and without --target_board=unix{-m32}, with no
> new failures. Ok for mainline?
OK.
Thanks,
Richard.
>
>
> 2022-09-13 Roger Sayle <roger@nextmovesoftware.com>
>
> gcc/ChangeLog
> * match.pd (op (lshift @0 @1) (lshift @2 @1)): Optimize the
> expression (X<<C) + (Y<<C) to (X+Y)<<C for signed types, that
> may have undefined overflow, provided that they don't trap.
>
> gcc/testsuite/ChangeLog
> * gcc.dg/pr71343-3.c: New test case.
>
>
> Thanks in advance,
> Roger
> --
>
next prev parent reply other threads:[~2022-09-14 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 18:37 Roger Sayle
2022-09-14 8:28 ` Richard Biener [this message]
2022-09-14 21:42 ` Marc Glisse
2022-09-15 6:39 ` Richard Biener
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='CAFiYyc2zjStxUqR=JO6Tpgfx0Rn6pitxXZPiWHxUzc7JW5N8LQ@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=roger@nextmovesoftware.com \
/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).