public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102809] Some TSVC benchmarks are slower after r12-4195-gec0124e0acb556cd
Date: Mon, 18 Oct 2021 10:57:30 +0000	[thread overview]
Message-ID: <bug-102809-4-2eXizVNYSQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102809-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #2)
> > Does this fix the problem?
> 
> Yes, it helps! Thank you for the patch.

Thanks for all your help here, and sorry for all the noise.  Getting the jump
threading restrictions in the presence of loops has been chore.

It seems we have finally agreed on what should be allowed, and Jeff is about to
approve the last bits.

Unfortunately, the next step is playing with the pipeline to see if we can
remove some threading passes.  This will probably unsettle things, but
hopefully not as much.

Again, thanks.

  parent reply	other threads:[~2021-10-18 10:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 10:14 [Bug tree-optimization/102809] New: " marxin at gcc dot gnu.org
2021-10-18 10:14 ` [Bug tree-optimization/102809] " marxin at gcc dot gnu.org
2021-10-18 10:17 ` aldyh at gcc dot gnu.org
2021-10-18 10:54 ` marxin at gcc dot gnu.org
2021-10-18 10:57 ` aldyh at gcc dot gnu.org [this message]
2021-10-18 11:04 ` [Bug tree-optimization/102809] [12 Regression] " rguenth at gcc dot gnu.org
2021-11-05 13:55 ` 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-102809-4-2eXizVNYSQ@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).