[PATCH] Prevent repetitive warnings for unrecognized processors and features (2nd attempt)

[Renato Golin]

On 3 February 2014 22:57, David Blaikie <dblaikie at gmail.com> wrote:

> Any reason not to just fix this in the frontend to begin with? (is it
> going to be substantially harder)
>

I was not involved on the original discussion, but I wonder... If a flag is
not recognized by the front-end, should it still be emitted to the
back-end? I think that Clang should emit a "cpu not recognized, default to
whatever cpu" warning and set the cpu to whatever default it should.

Of course, this is orthogonal to the bug in question, which should be fixed
even if the front-end stops being silly, as we do have (and can have) many
front-ends.

cheers,
--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140203/46c0e9cb/attachment.html>