public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102436] [11 Regression] Lost Load/Store Motion
Date: Fri, 19 Nov 2021 15:28:48 +0000	[thread overview]
Message-ID: <bug-102436-4-jFKlChiAvs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102436-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Sounds reasonable (not backporting, but holding bug open for now).  I'll
probably do some testing with it internally, so if you end up wanting to
revisit the backporting question, reach out I may have useful data.

  parent reply	other threads:[~2021-11-19 15:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 20:09 [Bug tree-optimization/102436] New: [11/12 " law at gcc dot gnu.org
2021-09-22  7:18 ` [Bug tree-optimization/102436] " rguenth at gcc dot gnu.org
2021-11-16 14:57 ` rguenth at gcc dot gnu.org
2021-11-19  8:35 ` cvs-commit at gcc dot gnu.org
2021-11-19  8:37 ` rguenth at gcc dot gnu.org
2021-11-19 15:28 ` law at gcc dot gnu.org [this message]
2022-04-21  7:50 ` [Bug tree-optimization/102436] [11 " rguenth at gcc dot gnu.org
2023-05-29 10:05 ` jakub 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-102436-4-jFKlChiAvs@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).