Displaying 3 results from an estimated 3 matches for "getdarwinv".
2009 Jun 16
0
[LLVMdev] PIC documentation ?
...look at the output I think. It's not considered part of the ABI, as
it doesn't affect the callee or the codegen for variable
definitions....note that the code sequences for function calls also
varied in compilers earlier than gcc-4.2, and OS's earlier than
Leopard. Look for getDarwinVers in the X86 and PPC back ends and look
around for "stubs" if you want to support Tiger.
int x;
void foo() {
return x;
}
Results on x86-32 with -fomit-frame-pointer (which is not the default):
result of -fPIC (equivalent to -fpic on Darwin):
_foo:
call L3
"L000000...
2009 Jun 16
4
[LLVMdev] PIC documentation ?
Anton,
>> Can I ask what platform ABI's are documented other than Itanium ?
> I'd bet all platform ABI are more or less documented.
Right.
Maybe we should collect references and do some LLVM PIC documentation and
put it on LLVM website ?
>> I need to get to understand PIC on x86, x86_64 and PowerPC for the COFF
>> and MachO backends.
> ABI is normally induced
2010 Sep 09
0
[LLVMdev] Knowing all possible libcalls in advance and __bzero
...does so:
libclamav JIT: Attempt to call external function __bzero
libclamav JIT: *** FATAL error encountered during bytecode generation
It turns out this is because Codegen has this:
const char *X86Subtarget::getBZeroEntry() const {
// Darwin 10 has a __bzero entry point for this purpose.
if (getDarwinVers() >= 10)
return "__bzero";
That belongs to simplifylibcalls. Is there any reason it has to
be in Codegen?
Also are there any other special cases like __bzero that is not part
of RTLIB::?
P.S.: More about the issue with libclamav:
libclamav has a strict policy of 0 external ca...