[Bug jit/65691] New: libgccjit documentation typo in gcc_jit_context_one

2015-04-08 Thread rur...@x-ray.at
: jit Assignee: dmalcolm at gcc dot gnu.org Reporter: rur...@x-ray.at Copy Paste problem. gcc_jit_rvalue *gcc_jit_context_one(gcc_jit_context *ctxt, gcc_jit_type *numeric_type) Given a numeric type (integer or floating point), get the rvalue for zero. Essentially this is just

[Bug middle-end/64463] New: Add warning: returns_nonnull attribute on a function compared against NULL

2015-01-01 Thread rur...@x-ray.at
: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: rur...@x-ray.at feature request: Working on gcc.gnu.org/bugzilla/show_bug.cgi?id=64459 I find it difficult to find all occurrences of wrong returns_nonnull attributes

[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] New: __attribute__((returns_nonnull)) creates wrong code on amd64

2014-12-31 Thread rur...@x-ray.at
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: rur...@x-ray.at I had to disable the new returns_nonnull on parrot with gcc 4.9 on amd64, but it does work fine with clang and the MSVC equivalent __notnull. I tried the gcc optimizations O0

[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