https://llvm.org/bugs/show_bug.cgi?id=28416
dmark...@mac.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #2 from dmark...@mac.com ---
we have a use case which is far more complicated than example I used in the bug
report, but even in my example
result of the malloc was used in the exit code of the program, clang shouldn't
alter logic of the program
it MUST return NULL if memory wasn't allocated and was used in the
next line of the code
from malloc man page:
RETURN VALUES
If successful, calloc(), malloc(), realloc(), reallocf(), and valloc()
functions return a pointer to
allocated memory. If there is an error, they return a NULL pointer and
set errno to ENOMEM.
so clang behavior isn't compliant to the malloc documentation
you're saying: "If the compiler can satisfy your use of malloc in a way which
doesn't end up calling malloc, that's ok."
problem is that in my example compiler didn't satisfy my use of malloc and
alter code flow which isn't acceptable
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
