[cfe-dev] Option -mtune
Sjoerd Meijer via cfe-dev
cfe-dev at lists.llvm.org
Wed Apr 22 09:13:44 PDT 2020
> For some of us, performance *is* correctness. :)
> IMO this option should emit a warning at least.
I obviously agree with that, but I don't see the benefit when that is emitted by using an opt-in flag, which was the consensus if I'm not mistaken.
So the absolute minimum we can do is to document this behaviour, which is what I did with rG35cf2f42dda4.
From: David Greene <david.greene at hpe.com>
Sent: 22 April 2020 16:59
To: David Blaikie <dblaikie at gmail.com>; Sjoerd Meijer <Sjoerd.Meijer at arm.com>
Cc: cfe-dev at lists.llvm.org Developers <cfe-dev at lists.llvm.org>
Subject: Re: [cfe-dev] Option -mtune
David Blaikie via cfe-dev <cfe-dev at lists.llvm.org> writes:
>> Thanks for your reply, and I can see that this is the only benefit of this
>> no-op: if your move to Clang and if you still have -mtune set in your build
>> environment, you don't get an "unknown option" error. But for me
>> personally, silently ignoring things and giving the impression it works is
>> worse than a simple Makefile fix, but maybe I am wrong, which is why I
>> checked here on the list.
> If it were a matter of correctness rather than performance, I'd agree -
For some of us, performance *is* correctness. :)
IMO this option should emit a warning at least.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev