[llvm-bugs] [Bug 47885] New: Sparc claims HasJIT=true, but doesn't have relocation support

via llvm-bugs llvm-bugs at lists.llvm.org
Fri Oct 16 14:28:06 PDT 2020


https://bugs.llvm.org/show_bug.cgi?id=47885

            Bug ID: 47885
           Summary: Sparc claims HasJIT=true, but doesn't have relocation
                    support
           Product: libraries
           Version: trunk
          Hardware: Sun
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: Backend: Sparc
          Assignee: unassignedbugs at nondot.org
          Reporter: andres at anarazel.de
                CC: llvm-bugs at lists.llvm.org, venkatra at cs.wisc.edu

Hi,

Due to a Debian build failure of Postgres, which uses LLVM for JIT compilation,
I noticed that the sparc target claims to have JIT support, but does not
actually support JIT compilation:

llvm/lib/Target/Sparc/TargetInfo/SparcTargetInfo.cpp :
extern "C" LLVM_EXTERNAL_VISIBILITY void LLVMInitializeSparcTargetInfo() {
  RegisterTarget<Triple::sparc, /*HasJIT=*/true> X(getTheSparcTarget(),
"sparc",
                                                   "Sparc", "Sparc");
  RegisterTarget<Triple::sparcv9, /*HasJIT=*/true> Y(
      getTheSparcV9Target(), "sparcv9", "Sparc V9", "Sparc");
  RegisterTarget<Triple::sparcel, /*HasJIT=*/true> Z(
      getTheSparcelTarget(), "sparcel", "Sparc LE", "Sparc");
}

but there's no relocation processing support at all:

llvm/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldELF.cpp
void RuntimeDyldELF::resolveRelocation(const SectionEntry &Section,
                                       uint64_t Offset, uint64_t Value,
                                       uint32_t Type, int64_t Addend,
                                       uint64_t SymOffset, SID SectionID) {

So it appears that HasJIT should be set to false instead?

Regards,

Andres

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20201016/738841a2/attachment.html>


More information about the llvm-bugs mailing list