search for: module_start

Displaying 3 results from an estimated 3 matches for "module_start".

Did you mean: module_stab
2011 Jul 01
2
[LLVMdev] Typo in IsLegalToCallImmediateAddr?
It seems that the || should be && here? /// IsLegalToCallImmediateAddr - Return true if the subtarget allows calls /// to immediate address. bool X86Subtarget::IsLegalToCallImmediateAddr(const TargetMachine &TM) const { if (Is64Bit) return false; return isTargetELF() || TM.getRelocationModel() == Reloc::Static; } For example, if you are doing ELF PIC (i.e. for a shared
2011 Jul 02
0
[LLVMdev] Typo in IsLegalToCallImmediateAddr?
On 2011-07-01 17:13, David Meyer wrote: > It seems that the || should be && here? > > /// IsLegalToCallImmediateAddr - Return true if the subtarget allows calls > /// to immediate address. > bool X86Subtarget::IsLegalToCallImmediateAddr(const TargetMachine &TM) const { > if (Is64Bit) > return false; > return isTargetELF() || TM.getRelocationModel() ==
2011 Oct 17
2
[LLVMdev] Typo in IsLegalToCallImmediateAddr?
...s 0x100: call 0x100 This requires a relocation of the value 0x100 - PC. (NOTE: this is NOT the same as: "foo: call foo+0x100", which requires no relocation) This can't be done correctly in PIC mode. If you do this in a shared library, the relocation is ignored and you get a jump to module_start + 0x100 instead of absolute 0x100. - pdox