public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105629] [13 Regression] g++.dg/opt/pr94589-2.C for cris, m68k, s390x
Date: Fri, 20 May 2022 11:43:46 +0000	[thread overview]
Message-ID: <bug-105629-4-P6pGERskj4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105629-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #2)
> On Thu, 19 May 2022, hp at gcc dot gnu.org wrote:
> I wonder if you can help and "bisect" the actual pattern that is now
> enabled for GENERIC folding?  The testcase is about spaceship optimization
> and the matching done in forwprop might be quite specific and in the need
> of a slight adjustment.

I'm going to interpret that as "if each pattern had its own #if
GIMPLE-wrapping, which hunk in the diff caused the regression".  I'll try and
see if it's as simple as it sounds.

  parent reply	other threads:[~2022-05-20 11:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 15:22 [Bug middle-end/105629] New: " hp at gcc dot gnu.org
2022-05-18 12:37 ` [Bug middle-end/105629] " rguenth at gcc dot gnu.org
2022-05-19 22:40 ` hp at gcc dot gnu.org
2022-05-20  6:07 ` rguenther at suse dot de
2022-05-20 11:43 ` hp at gcc dot gnu.org [this message]
2022-05-20 11:46 ` rguenther at suse dot de
2022-05-20 21:55 ` hp at gcc dot gnu.org
2022-05-21  1:26 ` hp at gcc dot gnu.org
2022-05-23  9:15 ` rguenth at gcc dot gnu.org
2022-05-24  6:20 ` cvs-commit at gcc dot gnu.org
2022-05-24  6:21 ` rguenth at gcc dot gnu.org
2022-05-24 14:02 ` hp 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-105629-4-P6pGERskj4@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).