public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brechtsanders at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/105858] MinGW-w64 64-bit build with --libstdcxx-pch: fatal error: cannot write PCH file: required memory segment unavailable
Date: Sat, 06 Aug 2022 10:02:39 +0000	[thread overview]
Message-ID: <bug-105858-4-yxZO0ZD6RM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105858-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105858

--- Comment #3 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
Some information I received related to this issue:

On 01/08/2022 14:52, Luis Dallos wrote:
>
>     PCH has had issues for as long as I can remember, see for example:
>
>     * https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-gcc/0010-Fix-using-large-PCH.patch
>
> The msys2 team commited in msys2/MINGW-packages@52908ed an additional patch in order to fix PCH relocation issues.
>
> https://github.com/msys2/MINGW-packages/blob/master/mingw-w64-gcc/0021-PR14940-Allow-a-PCH-to-be-mapped-to-a-different-addr.patch
>
> See also:
>
> msys2/MINGW-packages#11582 (comment)
> https://gcc.gnu.org/pipermail/gcc-patches/2022-May/594556.html

  parent reply	other threads:[~2022-08-06 10:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-05 19:13 [Bug c/105858] New: " brechtsanders at users dot sourceforge.net
2022-07-04  9:18 ` [Bug pch/105858] " brechtsanders at users dot sourceforge.net
2022-07-25  9:32 ` brechtsanders at users dot sourceforge.net
2022-08-06 10:02 ` brechtsanders at users dot sourceforge.net [this message]
2022-09-04  7:58 ` brechtsanders at users dot sourceforge.net
2022-09-04 13:53 ` brechtsanders at users dot sourceforge.net
2022-12-24  1:56 ` egor.pugin at gmail dot com
2022-12-26 15:02 ` brechtsanders at users dot sourceforge.net
2022-12-30 13:26 ` brechtsanders at users dot sourceforge.net

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-105858-4-yxZO0ZD6RM@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).