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

[marxin at gcc dot gnu.org via Gcc-bugs]

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

Martin Liška  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  ---
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.

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

[marxin at gcc dot gnu.org via Gcc-bugs]

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

Martin Liška  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  ---
I can take a look.

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

[jakub at gcc dot gnu.org via Gcc-bugs]

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

--- Comment #2 from Jakub Jelinek  ---
-fsanitize*= doesn't take an enum but comma separated list of enums though.

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

[pinskia at gcc dot gnu.org via Gcc-bugs]

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

Andrew Pinski  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  ---
This is true for almost all options that take an enum really.