public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105293] g++-8/i586: internal compiler error trying to compile with g++ (evtl. related to qt5/moc bug)
Date: Sat, 13 Apr 2024 01:17:10 +0000 [thread overview]
Message-ID: <bug-105293-4-X7TujryaNi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105293-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105293
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|WAITING |RESOLVED
Target Milestone|--- |9.0
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #6)
> Note that GCC 8 is no longer maintained and you should be using the last
> release from this branch, GCC 8.5. Can you check whether GCC 9.4 or later
> work correctly?
Since r9-1060-g31db0fe044cc9d, the code related to chkp (and
chkp_function_instrumented_p) is removed so I am going to assume this was fixed
for GCC 9.
Plus there is no testcase to prove it so just closing as invalid.
prev parent reply other threads:[~2024-04-13 1:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 18:31 [Bug c++/105293] New: " estellnb at elstel dot org
2022-04-16 18:56 ` [Bug c++/105293] " estellnb at elstel dot org
2022-04-17 9:35 ` estellnb at elstel dot org
2022-04-17 15:13 ` estellnb at elstel dot org
2022-04-17 18:31 ` estellnb at elstel dot org
2022-04-18 17:38 ` estellnb at elstel dot org
2022-04-19 9:25 ` rguenth at gcc dot gnu.org
2024-04-13 1:17 ` pinskia 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-105293-4-X7TujryaNi@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).