From: LIU Hao <lh_mouse@126.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Xi Ruoyao <xry111@xry111.site>,
GCC Patches <gcc-patches@gcc.gnu.org>, JonY <10walls@gmail.com>
Subject: Re: [PATCH] Remove size limit of PCH
Date: Wed, 11 May 2022 22:31:42 +0800 [thread overview]
Message-ID: <f05c0e99-a4be-97bb-9a15-90f9c1797260@126.com> (raw)
In-Reply-To: <Ynp2dghYz8EX3RAd@tucnak>
[-- Attachment #1.1: Type: text/plain, Size: 821 bytes --]
在 2022-05-10 22:28, Jakub Jelinek 写道:
>
> This looks reasonable, but doesn't contain the most important part.
> As mentioned in https://gcc.gnu.org/r12-5855
> the generic part can now support relocation of PCH, so it is fine if it is
> mapped at some other address, it is preferrable if it is mapped at the same
> address as it was written for, but if not, the generic code can relocate it.
>
> (... ...)
>
> IMHO you can just drop the loop, sleep of half a second is almost certainly
> slower than the relocation handling, so I'd just
Thanks for the hint. I have very little knowledge about how PCH works in GCC, thus I'm gonna propose
a patch to MSYS2 and see how it works. This can be committed to GCC later, after having been tested
through many packages.
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-05-11 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 11:35 LIU Hao
2022-05-10 12:00 ` Xi Ruoyao
2022-05-10 13:30 ` LIU Hao
2022-05-10 14:28 ` Jakub Jelinek
2022-05-11 14:31 ` LIU Hao [this message]
2022-05-11 11:44 ` Jonathan Yong
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=f05c0e99-a4be-97bb-9a15-90f9c1797260@126.com \
--to=lh_mouse@126.com \
--cc=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=xry111@xry111.site \
/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).