[llvm-dev] [cfe-dev] How to debug if LTO generate wrong code?

Rafael EspĂ­ndola via llvm-dev llvm-dev at lists.llvm.org
Tue Jun 7 08:04:42 PDT 2016

On 7 June 2016 at 10:54, Shi, Steven <steven.shi at intel.com> wrote:
> Hi Rafael,
> I finally enable the clang LTO build with small code model and  PIE, and my clang LTO Uefi firmware works now. Thank you! But I have one more issue on the clang normal build (without LTO) now. I find the small code model + "-fpie" build option will let clang generate some R_X86_64_GOTPCREL type relocation entries in my firmware image, which not happen in the clang LTO build. I wish I could enforce the clang normal build not to use the R_X86_64_GOTPCREL relocation type but to use R_X86_64_PC32 or R_X86_64_PLT32 instead. How could I do it?

Does it reproduce with clang trunk?


More information about the llvm-dev mailing list