On Jun 1, 2022, Hans-Peter Nilsson <h...@bitrange.com> wrote: > On Fri, 20 May 2022, Alexandre Oliva via Gcc-patches wrote: >> >> This patch introduces -multiflags, short for multilib TFLAGS, as an >> option that does nothing by default, but that can be added to TFLAGS >> and mapped to useful options by driver self-specs. >> >> I realize -m is reserved for machine-specific flags, which this option >> sort-of isn't, but its intended use is indeed to stand for >> machine-specific flags, so it's kind of ok. But that's just my >> official excuse, the reason I couldn't help picking it up is that it >> is a portmanteau of multi[lib] and TFLAGS.
> Ooh, a bikeshedding opportunity! :-) > Not liking the "-m"-space infringement: :-( > -fmultiflags? That works for me. I favored -multiflags slightly, because the intended use is for it to stand for other -m flags, but --multiflags AKA -fmultiflags will do as well. Now, is there interest in this feature? (As in, does it any make sense for me to post a revised patch, or should I keep it downstream?) -- Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/ Free Software Activist GNU Toolchain Engineer Disinformation flourishes because many people care deeply about injustice but very few check the facts. Ask me about <https://stallmansupport.org>
