https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108732
--- Comment #3 from Matt Hellige <matt at immute dot net> --- 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 does not seem to be a typical implication of a -o flag of any tool I've ever used. And in fact your suggested change sort of proves my point... Why would a user suspect that /dev/null can be used for both input and output of that gcc -xc invocation, but not the other one?
