https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69265
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Do you consider for options that take a Joined argument those corresponding
enum values?
I mean say provide hint for
-ftls-model=global-dinamic
to use
-ftls-model=global-dynamic
etc.? Harder will be options where the various enum values are not listed in
the *.opt file or somewhere easily accessible to the driver, say
-march=sandyridge
to use
-march=sandybridge
The question is if for the joined options you should build all the possible
options joined with all the possible arguments and then hint among that, or if
you just should handle = sign specially and in this case also look at
-sanitize=
vs. -fsanitize= and separately for misspellings in the argument.
The -fsanitize= arguments are even more complicated because they actually don't
allow just one joined string, but allow
-fsanitize=integer-divide-by-zero,address,shift
etc.
