[patch] Forward all -f* options to -cc1

Reid Kleckner rnk at google.com
Fri Sep 27 15:22:50 PDT 2013

I don't see any reason to have a separate .td file for -f flags.  Why not
make it easier to represent -f flags in the existing Options.td file?

-W flags are special because they are already in their own domain-specific
.td file.  I don't think that's a precedent worth following.

On Fri, Sep 27, 2013 at 2:20 PM, Rafael EspĂ­ndola <
rafael.espindola at gmail.com> wrote:

> This is the first patch for trying to implement a regular treatment of
> -f/-fno- options. It just forwards all -f options to -cc1 and, for
> now, produces a more specific error in -cc1.
> The next step is to add a .td file with flags and tablegen it to an
> enum and an feature parser that returns one of the enums. Using that
> parseFFlagOptions should then be able to, still manually, set the
> appropriate bits in the *Options objects.
> Cheers,
> Rafael
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20130927/a8896752/attachment.html>

More information about the cfe-commits mailing list