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/110009] Another missing ABS detection
Date: Mon, 04 Sep 2023 18:10:42 +0000	[thread overview]
Message-ID: <bug-110009-4-d0KqrMJHWV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110009-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |98907

--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #6)
> Vector testcases too:
> 
> Which does work with the match pattern in comment #5.


Except veclowering messes up ABSU, see PR 111285 for that.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98907
[Bug 98907] Failure to optimize abs pattern

      parent reply	other threads:[~2023-09-04 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-28  0:18 [Bug tree-optimization/110009] New: " pinskia at gcc dot gnu.org
2023-05-28  9:36 ` [Bug tree-optimization/110009] " gjl at gcc dot gnu.org
2023-05-28 14:38 ` pinskia at gcc dot gnu.org
2023-07-12  6:26 ` pinskia at gcc dot gnu.org
2023-09-04  8:20 ` pinskia at gcc dot gnu.org
2023-09-04  8:39 ` pinskia at gcc dot gnu.org
2023-09-04  9:00 ` pinskia at gcc dot gnu.org
2023-09-04 18:09 ` pinskia at gcc dot gnu.org
2023-09-04 18:10 ` 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-110009-4-d0KqrMJHWV@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).