https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108732
--- Comment #7 from Matt Hellige ---
Those make sense as internal details. I don't think a typical user should be
expected to guess or learn these differences in order to use the GCC from the
command line. So, whether or not they suffice as just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108732
--- Comment #5 from Matt Hellige ---
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:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108732
--- Comment #3 from Matt Hellige ---
As long as I'm updating builds, I'll switch to that invocation, thanks.
I still do think it's a little odd that in this case (and *only* in this case?)
output needs to be written to a mappable file. That doe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108732
Bug ID: 108732
Summary: Pre-compiled headers cannot be output to /dev/null
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
