[Bug c/64459] __attribute__((returns_nonnull)) creates wrong code on amd64

2015-01-19 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64459 Jakub Jelinek jakub at gcc dot gnu.org changed: What|Removed |Added CC||jakub at gcc dot

[Bug c/64459] __attribute__((returns_nonnull)) creates wrong code on amd64

2015-01-01 Thread rur...@x-ray.at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64459 --- Comment #4 from Reini Urban rur...@x-ray.at --- maybe the script is of value to anyone: https://gist.github.com/rurban/b8b951d03ff22734f05b

[Bug c/64459] __attribute__((returns_nonnull)) creates wrong code on amd64

2014-12-31 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64459 Andrew Pinski pinskia at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |WAITING

[Bug c/64459] __attribute__((returns_nonnull)) creates wrong code on amd64

2014-12-31 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64459 --- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org --- Maybe parrot has some code it where returns_nonnull is on the function but it actually can return null and clang/MSVC does not optimize as good as GCC does.

[Bug c/64459] __attribute__((returns_nonnull)) creates wrong code on amd64

2014-12-31 Thread rur...@x-ray.at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64459 Reini Urban rur...@x-ray.at changed: What|Removed |Added Status|WAITING |RESOLVED