Displaying 2 results from an estimated 2 matches for "rigic".
Did you mean:
rigid
2009 Jun 10
0
[LLVMdev] Call to address 0 gets removed
...fficult to
avoid certain C-specific assumptions.
Let's take your examples. The assumption that alloca never produces
null seems like a reasonable cross-language assumption to me, based on
alloca's status as a compiler-defined (and totally unstandardized)
intrinsic; if I need more rigic semantics, I shouldn't be using
alloca. The assumption that the function called malloc never returns
aliasing pointers is indeed a C-specific assumption, but it's one that
I can easily avoid if necessary by, well, not using C-specific libcall
optimizations. And most of these C-ins...
2009 Jun 10
2
[LLVMdev] Call to address 0 gets removed
2009/6/10 John McCall <rjmccall at apple.com>
> There's another point that hasn't been raised yet here, which is that
> the
> undefinedness of calling (void*) 0 is a property of C, not necessarily
> of
> the LLVM abstract language. I think you can make an excellent case that
> the standard optimizations should not be enforcing C language semantics,
> or at