https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111049
--- Comment #2 from Mark Pizzolato ---
> Looks like this is fixed for GCC 11.
The latest Raspberry Pi OS is still packaging gcc 10.2.1.
How was this tested with gcc 11?
Was there a specific change that addressed the problem? If so, can we ge
: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: mark at infocomm dot com
Target Milestone: ---
Created attachment 55746
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55746&action=edit
C
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744
--- Comment #9 from Mark Pizzolato ---
> When val == 0 then the case of len == 0 is ambiguous and you can't really
tell the user they swapped val and len (because they are equal).
That is certainly true.
I'm not sure how that specifically relate
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744
--- Comment #7 from Mark Pizzolato ---
Thanks for reducing this test case further. That illuminates something for me:
Specifically:
Notice in the following lines:
if (__builtin_constant_p (__len) && __len == 0
&& (!__builtin_constant_p
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744
Mark Pizzolato changed:
What|Removed |Added
CC||mark at infocomm dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744
--- Comment #2 from Mark Pizzolato 2012-10-23
16:42:06 UTC ---
Created attachment 28514
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28514
MUCH simpler test case
