public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug pch/71934] pch cannot be disabled so gcc cannot be position independent Date: Mon, 06 Dec 2021 09:43:10 +0000 [thread overview] Message-ID: <bug-71934-4-Ncb3JNOmAK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-71934-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71934 --- Comment #27 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #26) > Note, the code to emit that relocation table isn't for free, besides that > ~3% growth of the *.gch files it also slows down the PCH generation, e.g. > for stdc++.h at -O2 -g on my box from ~3.45s to ~4.13s, so some 20%, I bet > mainly to qsort the array of ~2.5 million pointers. the one CS problem indirection cannot solve is having too many pointers ;). Do you have a feel for what the growth in time is for the whole parse+output? (we assume that PCH remains useful so long as the read-in is quicker than that, right?) > But upon PCH restore it shouldn't be noticeable, it is one size_t fread and > one fseek when no relocation is needed.
next prev parent reply other threads:[~2021-12-06 9:43 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-71934-4@http.gcc.gnu.org/bugzilla/> 2021-08-29 4:00 ` egallager at gcc dot gnu.org 2021-09-02 13:39 ` iains at gcc dot gnu.org 2021-09-02 17:39 ` jakub at gcc dot gnu.org 2021-12-03 10:06 ` cvs-commit at gcc dot gnu.org 2021-12-03 13:28 ` hjl.tools at gmail dot com 2021-12-03 13:30 ` jakub at gcc dot gnu.org 2021-12-03 13:42 ` iains at gcc dot gnu.org 2021-12-03 13:46 ` hjl.tools at gmail dot com 2021-12-03 14:02 ` iains at gcc dot gnu.org 2021-12-03 14:03 ` jakub at gcc dot gnu.org 2021-12-03 14:10 ` iains at gcc dot gnu.org 2021-12-03 14:14 ` jakub at gcc dot gnu.org 2021-12-04 15:53 ` jakub at gcc dot gnu.org 2021-12-05 12:51 ` iains at gcc dot gnu.org 2021-12-05 14:44 ` iains at gcc dot gnu.org 2021-12-05 14:52 ` jakub at gcc dot gnu.org 2021-12-05 15:22 ` iains at gcc dot gnu.org 2021-12-05 15:30 ` jakub at gcc dot gnu.org 2021-12-05 20:40 ` jakub at gcc dot gnu.org 2021-12-06 8:43 ` jakub at gcc dot gnu.org 2021-12-06 9:23 ` jakub at gcc dot gnu.org 2021-12-06 9:35 ` jakub at gcc dot gnu.org 2021-12-06 9:43 ` iains at gcc dot gnu.org [this message] 2021-12-06 10:21 ` cvs-commit at gcc dot gnu.org 2021-12-09 14:44 ` cvs-commit at gcc dot gnu.org 2021-12-09 14:56 ` cvs-commit at gcc dot gnu.org 2021-12-09 15:25 ` cvs-commit at gcc dot gnu.org 2021-12-09 15:43 ` iains at gcc dot gnu.org 2021-12-09 16:57 ` cvs-commit 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-71934-4-Ncb3JNOmAK@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: linkBe 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).