[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2014-08-06 Thread amodra at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744 Alan Modra changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2014-03-24 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744 --- Comment #10 from Richard Biener --- It's a GNU ld bug I believe. https://sourceware.org/bugzilla/show_bug.cgi?id=16746

[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2014-03-24 Thread mark at infocomm dot com
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

[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2014-03-24 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744 --- Comment #8 from Richard Biener --- (In reply to Mark Pizzolato from comment #7) > Thanks for reducing this test case further. That illuminates something for > me: > > Specifically: > > Notice in the following lines: > > if (__builtin_con

[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2014-03-24 Thread mark at infocomm dot com
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

[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2014-03-24 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744 --- Comment #6 from Richard Biener --- Btw, it works when using gold ...

[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2014-03-21 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744 Richard Biener changed: What|Removed |Added Known to fail||4.7.3, 4.8.3, 4.9.0 Severity|n

[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2014-03-21 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744 --- Comment #5 from Richard Biener --- It also (sadly) means this "works" with -fno-use-linker-plugin. It also means that not outputting the UNDEF into the LTO symbol table for this case doesn't work as the executable will not link (we optimize t

[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2014-03-21 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744 --- Comment #4 from Richard Biener --- typedef __SIZE_TYPE__ size_t; extern void *memset (void *__s, int __c, size_t __n) __attribute__ ((__nothrow__)) __attribute__ ((__nonnull__ (1))); extern void __warn_memset_zero_len (void) __attribute__((__w

[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2012-10-23 Thread mark at infocomm dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744 Mark Pizzolato changed: What|Removed |Added CC||mark at infocomm dot com --- C

[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2012-10-23 Thread 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

[Bug lto/51744] Erroneous warning: memset used with constant zero length parameter

2012-01-04 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51744 Richard Guenther changed: What|Removed |Added Keywords||diagnostic, lto Status|UNC