[Bug c/44081] Incorrect nonnull assumed in code generation

2010-05-11 Thread hv at crypt dot org
--- Comment #4 from hv at crypt dot org 2010-05-11 15:38 --- (In reply to comment #3) > That's a user bug. You shouldn't pass NULL to arguments declared nonnull. > To quote gcc documentation: > "The compiler may also choose to make optimizations based > on the knowledge that certain fun

[Bug c/44081] Incorrect nonnull assumed in code generation

2010-05-11 Thread jakub at gcc dot gnu dot org
--- Comment #3 from jakub at gcc dot gnu dot org 2010-05-11 14:51 --- That's a user bug. You shouldn't pass NULL to arguments declared nonnull. To quote gcc documentation: "The compiler may also choose to make optimizations based on the knowledge that certain function arguments will not

[Bug c/44081] Incorrect nonnull assumed in code generation

2010-05-11 Thread hv at crypt dot org
--- Comment #2 from hv at crypt dot org 2010-05-11 14:41 --- Created an attachment (id=20631) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20631&action=view) Generated assembly code, with annotation -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44081

[Bug c/44081] Incorrect nonnull assumed in code generation

2010-05-11 Thread hv at crypt dot org
--- Comment #1 from hv at crypt dot org 2010-05-11 14:41 --- Created an attachment (id=20630) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20630&action=view) C source code -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44081