On 8/31/22 10:24 AM, Segher Boessenkool wrote: > Should *any* explicit command line flag ever be disabled like that? > (Not talking about things like -m32 -m64, ...
In a general sense, I'd agree that the answer is no, but we do have dependent options like -maltivec and -mvsx, etc., so a -mno-altivec better disable any explicit -mvsx earlier on the command line. Ditto for -msoft-float better disable any -maltivec and -mvsx, etc. It's complicated...and that's a bad thing. :-( > -mpowerpc64 -m32 should always mean the same as -m32 -mpowerpc64, that's > the principle of least surprise. I think I agree with this, since -mpowerpc64 doesn't mean or imply -m64. I say "think", because I don't remember the history of why it behaves this way and maybe there was a reason we did like this? If there isn't a reason, then I'm all for -m32 not overriding -mpowerpc64. Peter
