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/110760] slp introduces new overflow arithmetic
Date: Thu, 20 Jul 2023 23:46:43 +0000 [thread overview]
Message-ID: <bug-110760-4-dDD9CfOPtC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110760-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110760
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Krister Walfridsson from comment #3)
> (In reply to Andrew Pinski from comment #1)
> > I thought we decided that vector types don't apply the overflow rules and
> > always just wrap ...
>
> That makes sense. But on the other hand, PR 110495 is a similar issue, and
> that was fixed...
>
> And TYPE_OVERFLOW_WRAPS should return true for integer vectors if they
> always wrap (or is it only valid for scalars? But ANY_INTEGRAL_TYPE_P is
> careful to handle vectors and complex numbers too, so I thought the
> ANY_INTEGRAL_TYPE_CHECK in TYPE_OVERFLOW_WRAPS means that it work for
> vectors too).
That is slightly different, it was introducing -2(OVF) too.
next prev parent reply other threads:[~2023-07-20 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 22:42 [Bug tree-optimization/110760] New: slp introduces new wrapped arithmetic kristerw at gcc dot gnu.org
2023-07-20 22:45 ` [Bug tree-optimization/110760] " pinskia at gcc dot gnu.org
2023-07-20 22:46 ` [Bug tree-optimization/110760] slp introduces new overflow arithmetic pinskia at gcc dot gnu.org
2023-07-20 23:29 ` kristerw at gcc dot gnu.org
2023-07-20 23:46 ` pinskia at gcc dot gnu.org [this message]
2023-07-21 7:03 ` 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-110760-4-dDD9CfOPtC@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).