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: -frob-multiflags? -forward-multiflags? or why not just -fmultiflags? brgds, H-P
