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/108354] [13 Regression] Dead Code Elimination Regression at -O2 since r13-89-gb3e98eb3396e16
Date: Tue, 31 Jan 2023 08:23:32 +0000	[thread overview]
Message-ID: <bug-108354-4-7mTnIS6Nzr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108354-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> This is a specific case of PR 91213 and the case which will also fix PR
> 96921:
> 
> /* 1 - a is a ^ 1 if a had a bool range. */
> (simplify
>  (minus integer_onep@0 SSA_NAME@1)
>   (if (INTEGRAL_TYPE_P (type)
>        && ssa_name_has_boolean_range (@1))
>    (bit_xor @1 @0)))

I might be running into an Ada build failure with this patch; I am double
checking this now. It also could be a latent bug ...

  parent reply	other threads:[~2023-01-31  8:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 12:41 [Bug tree-optimization/108354] New: Dead Code Elimination Regression at -O2 (trunk vs. 12.2.0) yann at ywg dot ch
2023-01-10 14:44 ` [Bug tree-optimization/108354] [13 Regression] Dead Code Elimination Regression at -O2 since r13-89-gb3e98eb3396e16 marxin at gcc dot gnu.org
2023-01-31  4:33 ` pinskia at gcc dot gnu.org
2023-01-31  4:52 ` pinskia at gcc dot gnu.org
2023-01-31  8:23 ` pinskia at gcc dot gnu.org [this message]
2023-01-31 20:01 ` pinskia at gcc dot gnu.org
2023-01-31 20:06 ` pinskia at gcc dot gnu.org
2023-01-31 20:07 ` pinskia at gcc dot gnu.org
2023-02-14 21:47 ` pinskia at gcc dot gnu.org
2023-02-14 21:48 ` pinskia 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-108354-4-7mTnIS6Nzr@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).