public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98069] [8/9/10 Regression] Miscompilation with -O3 since r8-2380-g2d7744d4ef93bfff
Date: Fri, 23 Apr 2021 09:20:49 +0000 [thread overview]
Message-ID: <bug-98069-4-jgtuu1jyrr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98069-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98069
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|8.5 |10.4
--- Comment #7 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
As discussed on irc, the fix was quite invasive, so it seems a bit
dangerous to backport further than GCC 10. Will backport to GCC 10 in
the GCC 11.2 timeframe, once we've had more chance to see if there's
any fallout.
next prev parent reply other threads:[~2021-04-23 9:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 15:04 [Bug tree-optimization/98069] New: Miscompilation with -O3 vsevolod.livinskij at frtk dot ru
2020-11-30 16:29 ` [Bug tree-optimization/98069] [8/9/10/11 Regression] Miscompilation with -O3 since r8-2380-g2d7744d4ef93bfff marxin at gcc dot gnu.org
2020-11-30 16:29 ` marxin at gcc dot gnu.org
2020-12-01 8:33 ` rguenth at gcc dot gnu.org
2020-12-01 8:33 ` rguenth at gcc dot gnu.org
2020-12-01 9:41 ` rguenth at gcc dot gnu.org
2020-12-02 8:38 ` rguenth at gcc dot gnu.org
2020-12-04 13:23 ` rguenth at gcc dot gnu.org
2021-01-08 14:39 ` rguenth at gcc dot gnu.org
2021-04-23 9:20 ` rsandifo at gcc dot gnu.org [this message]
2021-04-23 9:21 ` [Bug tree-optimization/98069] [8/9/10 " rsandifo at gcc dot gnu.org
2021-04-23 9:21 ` rsandifo at gcc dot gnu.org
2022-06-28 10:42 ` [Bug tree-optimization/98069] [10 " jakub at gcc dot gnu.org
2023-07-07 9:15 ` 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-98069-4-jgtuu1jyrr@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).