public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/95084] [11/12 Regression] code sinking prevents if-conversion
Date: Tue, 01 Feb 2022 07:31:28 +0000	[thread overview]
Message-ID: <bug-95084-4-DlNRGgmja4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95084-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note the issue is older but there are some cases where sink didn't do its job
that have been fixed meanwhile.

For GCC 12 we have an additional (albeit quite late) sinking pass, so one
option might be to tame down early sinking for possibly trapping operations in
loops that look like they could be vectorized (similar how we tame PRE).

I think the only loop pass affected by not sinking might be unswitching which
could get less favorable costs due to the need to duplicate the not sunk stmts.

At least I cannot think of a way to preserve the conditional non-trappingness
on the ref after sinking it.

  parent reply	other threads:[~2022-02-01  7:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 13:46 [Bug tree-optimization/95084] New: " rguenth at gcc dot gnu.org
2022-01-31 15:24 ` [Bug tree-optimization/95084] [11/12 Regression] " rsandifo at gcc dot gnu.org
2022-01-31 21:02 ` pinskia at gcc dot gnu.org
2022-02-01  7:31 ` rguenth at gcc dot gnu.org [this message]
2022-04-21  7:47 ` rguenth at gcc dot gnu.org
2022-07-06 21:17 ` [Bug tree-optimization/95084] [11/12/13 " pinskia at gcc dot gnu.org
2023-05-29 10:02 ` [Bug tree-optimization/95084] [11/12/13/14 " jakub at gcc dot gnu.org
2023-08-04 17:26 ` 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-95084-4-DlNRGgmja4@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).