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 pch/101183] [compiler ICE]gcc mingw for precompiled header file. MapViewOfFileEx: Attempt to access invalid address.
Date: Wed, 23 Jun 2021 23:45:42 +0000 [thread overview]
Message-ID: <bug-101183-4-C7W8IuSLIV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101183-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101183
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to cqwrteur from comment #2)
> https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-gcc/0010-Fix-
> using-large-PCH.patch
> But why not add these patches to GCC itself?
You have to ask the mingw project that question. Have them submit them to gcc.
prev parent reply other threads:[~2021-06-23 23:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 21:47 [Bug preprocessor/101183] New: gcc " unlvsur at live dot com
2021-06-23 21:53 ` [Bug pch/101183] [compiler ICE]gcc " pinskia at gcc dot gnu.org
2021-06-23 23:43 ` unlvsur at live dot com
2021-06-23 23:45 ` 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-101183-4-C7W8IuSLIV@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).