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/108732] Pre-compiled headers cannot be output to /dev/null
Date: Wed, 08 Feb 2023 23:01:19 +0000	[thread overview]
Message-ID: <bug-108732-4-ehI5I2SRge@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108732-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Matt Hellige from comment #5)
> That makes sense, but it's just a strange inconsistency from a usability
> point of view.
> 
> .so files are generally mmapped as well, I believe, aren't they? But I can
> still generate one to /dev/null if I like:
> 
>    $ gcc12.2.0 -o /dev/null -rdynamic -shared foo.o bar.o -lrt ...
> 
> Works fine.

Well so works differently because the linker produces runtime relocations for
some segments of the shared objects which get applied at runtime. This is
unlike pch which does have a relocation method but that method is slow. Also
the linker is basically doing copies from other files into the final file while
gcc is outputting its internals out for pch.

  parent reply	other threads:[~2023-02-08 23:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 21:59 [Bug c/108732] New: " matt at immute dot net
2023-02-08 22:09 ` [Bug pch/108732] " pinskia at gcc dot gnu.org
2023-02-08 22:11 ` pinskia at gcc dot gnu.org
2023-02-08 22:23 ` matt at immute dot net
2023-02-08 22:45 ` pinskia at gcc dot gnu.org
2023-02-08 22:56 ` matt at immute dot net
2023-02-08 23:01 ` pinskia at gcc dot gnu.org [this message]
2023-02-08 23:15 ` matt at immute dot net
2023-05-22 23:16 ` justinpopo6 at gmail dot com

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-108732-4-ehI5I2SRge@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).