[Bug sanitizer/101103] New: -fsanitise=undef gives better help than -fsanitize=undef

[Bug sanitizer/101103] New: -fsanitise=undef gives better help than -fsanitize=undef

[segher at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101103

            Bug ID: 101103
           Summary: -fsanitise=undef gives better help than
                    -fsanitize=undef
           Product: gcc
           Version: 9.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: segher at gcc dot gnu.org
                CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
  Target Milestone: ---

-fsanitise=undef gives
  gcc: error: unrecognized command line option '-fsanitise=undef'; did you mean
'-
fsanitize=undefined'?

while -fsanitize=undef gives just
  gcc: error: unrecognized argument to '-fsanitize=' option: 'undef'

[Bug driver/101103] -fsanitise=undef gives better help than -fsanitize=undef

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101103

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |diagnostic
   Last reconfirmed|                            |2021-06-16
     Ever confirmed|0                           |1
          Component|sanitizer                   |driver
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This is true for almost all options that take an enum really.

[Bug driver/101103] -fsanitise=undef gives better help than -fsanitize=undef

[jakub at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101103

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
-fsanitize*= doesn't take an enum but comma separated list of enums though.

[Bug driver/101103] -fsanitise=undef gives better help than -fsanitize=undef

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101103

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |marxin at gcc dot gnu.org
             Status|NEW                         |ASSIGNED

--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
I can take a look.

[Bug driver/101103] -fsanitise=undef gives better help than -fsanitize=undef

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101103

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|marxin at gcc dot gnu.org          |unassigned at gcc dot gnu.org
             Status|ASSIGNED                    |NEW

--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Ok, so the reason is following:
- in case of -fsanitise=undef, we don't have an option match as so we search in
all possible options and their values, that's why have a match
- in case of -fsanitize=undef, we first match -fsanitize and then
get_closest_sanitizer_option is called; the function only compares option
values and we don't have a match for 'undefined' as 'undef' does not reach
distance threshold.

It's a limitation, but having low priority to me.