Re: [llvm-commits] CVS: llvm/lib/Target/X86/X86Subtarget.cpp X86Subtarget.h X86TargetMachine.cpp

2006-12-20 Thread Evan Cheng
Ok. I see PPC does exactly the same thing. But this seems like a temporary solution. Could we add some kind of JIT relocation model which are target specific? Or any method that would allow llc to codegen (by specifying some command line option?) in the exact same way as the JIT would?

Re: [llvm-commits] CVS: llvm/lib/Target/X86/X86Subtarget.cpp X86Subtarget.h X86TargetMachine.cpp

2006-12-20 Thread Anton Korobeynikov
Hello, Chris. PPC64 has a similar problem. It wants to do codegen in PIC mode, but it doesn't want the JIT to make dyld stubs. As such, it does 'JIT PIC' mode, which is like PIC but doesn't do the extra load to go through dyld stubs. Yes, It's quite the same. At codegen level we know

Re: [llvm-commits] CVS: llvm/lib/Target/X86/X86Subtarget.cpp X86Subtarget.h X86TargetMachine.cpp

2006-12-20 Thread Evan Cheng
I took a look at mingw related code. It seems to me for mingw that you can set relocation type to pic for llc and static for jit. No? Then GVRequiresExtraLoad can just check relocation type? Also GVRequiresExtraLoad now violates 80-col policy and its style is inconsistent with the rest of

Re: [llvm-commits] CVS: llvm/lib/Target/X86/X86Subtarget.cpp X86Subtarget.h X86TargetMachine.cpp

2006-12-20 Thread Chris Lattner
On Dec 20, 2006, at 12:25 AM, Evan Cheng wrote: Ok. I see PPC does exactly the same thing. But this seems like a temporary solution. Could we add some kind of JIT relocation model which are target specific? Or any method that would allow llc to codegen (by specifying some command line