r191394 - Produce an error for unknown -f options.
rafael.espindola at gmail.com
Thu Sep 26 06:16:32 PDT 2013
I implemented most of them in r191429.
I left out:
* -fplugin-*: clang plugins are different from gcc. We should probably
err on someone trying to pass us a gcc plugin.
* -fbuiltin-*: I could not find an easy way to get the list that gcc supports.
* options that gcc itself errs on (like the -fwarn-incomplete-patterns)
* options we already implemented (like -fasynchronous-unwind-tables)
Were you grepping error logs?
On 25 September 2013 22:07, Nick Lewycky <nlewycky at google.com> wrote:
> On 25 September 2013 18:53, Rafael Espíndola <rafael.espindola at gmail.com>
>> >> Err, we aren't ready for this. If we're going to do this, could you
>> >> stage
>> >> it such that the gcc flags are added but ignored, then we error on
>> >> unknown
>> >> options?
>> > This is already how it works. If our list of ignored gcc -f flags isn't
>> > complete enough, that's simple to fix.
>> I am happy to revert if needed, but as Eli pointed out adding ignored
>> options is really easy. Do you have a list?
> Using regex syntax:
> and the -fno- versions of each of these. I may also be missing more, but
> this is a start.
More information about the cfe-commits