https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105997
--- Comment #6 from Andrew Pinski ---
Also people who assume the compiler is broken ask them to try
-fsanitize=address and other sanitizers really. Gcc does is more "sensitive" to
undefined behavior and more bugs in the user code does happen.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105997
--- Comment #5 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #3)
> If anybody wants to turn it into a proper bug report, the original commit
> (and description) is at
> https://github.com/zynaddsubfx/zynaddsubfx/commit/
> 22
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105997
--- Comment #4 from Jonathan Wakely ---
(In reply to Andreas Schwab from comment #2)
> This line is definitely a bug in ZynAddSubFX:
>
> 1154:bool is_dir = fn->d_type & DT_DIR;
>
> d_type is not a bitfield.
Not all systems even have a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105997
--- Comment #3 from Jonathan Wakely ---
If anybody wants to turn it into a proper bug report, the original commit (and
description) is at
https://github.com/zynaddsubfx/zynaddsubfx/commit/22a5f8da76c16c47c3814eedaec8f9fe0ff4248b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105997
--- Comment #2 from Andreas Schwab ---
This line is definitely a bug in ZynAddSubFX:
1154:bool is_dir = fn->d_type & DT_DIR;
d_type is not a bitfield.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105997
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRME
