[Bug sanitizer/69508] Undefined Behavior Sanitizer __ubsan_handle_load_invalid_value reports invalid load with wrong value

[chris.bainbridge at gmail dot com]

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

Chris Bainbridge  changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
 Resolution|--- |INVALID

--- Comment #3 from Chris Bainbridge  ---
Thanks for the hints. Jakub was right - after casting with "*(char *)&" the
value is indeed 2.

Marking this bug report as invalid.

[Bug sanitizer/69508] Undefined Behavior Sanitizer __ubsan_handle_load_invalid_value reports invalid load with wrong value

[jakub at gcc dot gnu.org]

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

--- Comment #2 from Jakub Jelinek  ---
Note that passing the _Bool to varargs function might very well zero extend it
(i.e. mask with 1).  As kernel is built with -fno-strict-aliasing, I bet
trying to print *(char *)&tid_agg_rx->removed instead might give you more
accurate answers.

[Bug sanitizer/69508] Undefined Behavior Sanitizer __ubsan_handle_load_invalid_value reports invalid load with wrong value

[rguenth at gcc dot gnu.org]

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

Richard Biener  changed:

   What|Removed |Added

 Status|UNCONFIRMED |WAITING
   Last reconfirmed||2016-01-27
 Ever confirmed|0   |1

[Bug sanitizer/69508] Undefined Behavior Sanitizer __ubsan_handle_load_invalid_value reports invalid load with wrong value

[pinskia at gcc dot gnu.org]

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

--- Comment #1 from Andrew Pinski  ---
Can you provide the preprocessed source?