public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88132] Compile time and memory hog w/ var-tracking on 32-bit targets
Date: Wed, 26 Oct 2022 05:47:01 +0000 [thread overview]
Message-ID: <bug-88132-4-oh3UspToWt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-88132-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88132
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linkw at gcc dot gnu.org
--- Comment #3 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Arseny Solokha from comment #2)
> I cannot reproduce it anymore w/ gcc 13.0.0 20221016 snapshot
> (g:6366e3e8847af98d4728d55951534769d034d02a) and w/ gcc 12.2.
Should we check the release branches gcc-10 and gcc-11? Or can we just
aggressively close this? since the original release gcc-9 which this PR was
opened against isn't an active branch any more and this issue doesn't exist on
latest branch gcc-12 and trunk?
prev parent reply other threads:[~2022-10-26 5:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-88132-4@http.gcc.gnu.org/bugzilla/>
2022-10-19 4:17 ` asolokha at gmx dot com
2022-10-26 5:47 ` linkw at gcc dot gnu.org [this message]
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-88132-4-oh3UspToWt@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).