public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lhyatt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/115312] [14/15 Regression] ICE when including a PCH via compiler option -include
Date: Sat, 15 Jun 2024 15:30:46 +0000 [thread overview]
Message-ID: <bug-115312-4-IWNRfLh85v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115312-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115312
--- Comment #5 from Lewis Hyatt <lhyatt at gcc dot gnu.org> ---
(In reply to Brecht Sanders from comment #4)
> No, that patch wasn't added for my build, see my build recipe here:
> https://github.com/brechtsanders/winlibs_recipes/blob/main/recipes/gcc.winlib
Thanks, this script is useful. FWIW I think the patch is there, line 778?
Unless I am missing something.
I see you also commented out the assert in your recipe. I am still not sure if
that is just masking some deeper issue, but I am getting close to being able to
reproduce it myself and will let you know.
next prev parent reply other threads:[~2024-06-15 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 3:37 [Bug pch/115312] New: " gcc at mailinator dot com
2024-06-02 1:26 ` [Bug pch/115312] " lhyatt at gcc dot gnu.org
2024-06-03 7:09 ` rguenth at gcc dot gnu.org
2024-06-11 4:28 ` brechtsanders at users dot sourceforge.net
2024-06-11 21:37 ` lhyatt at gcc dot gnu.org
2024-06-15 13:14 ` brechtsanders at users dot sourceforge.net
2024-06-15 15:30 ` lhyatt at gcc dot gnu.org [this message]
2024-06-15 19:41 ` brechtsanders at users dot sourceforge.net
2024-06-17 16:33 ` [Bug pch/115312] [14/15 Regression] ICE when including a PCH via compiler option -include since r14-5836 lhyatt at gcc dot gnu.org
2024-06-27 21:07 ` lhyatt 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-115312-4-IWNRfLh85v@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).