[LLVMbugs] [Bug 9951] New: "LLVM ERROR: unsupported relocation of variable" from llc as of @131140

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Thu May 19 09:06:12 PDT 2011


http://llvm.org/bugs/show_bug.cgi?id=9951

           Summary: "LLVM ERROR: unsupported relocation of variable" from
                    llc as of @131140
           Product: new-bugs
           Version: trunk
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: matt at pharr.org
                CC: llvmbugs at cs.uiuc.edu


As of a recent update to dev TOT, I'm seeing this error whenever I try to
generate debugging information with my compiler.  Attached is a test case that
reproduces when run through llc.  (It is possible that I have a bug in how I
generate debugging metadata that is only being exposed by recent changes to
LLVM, but
the debug info I generated previously seemed to generally work correctly.)

I've attached a test case, that if run through llc to generate a native object
file, gives this error:

% llc bugpoint-reduced-simplified.ll  -o a.o -filetype=obj 
LLVM ERROR: unsupported relocation of variable 'Ltmp7'
%

I've searched through recent checkins and it seems that this was introduced by
the changes in 131140:

Author: Rafael Espindola <rafael.espindola at gmail.com>
Date:   Tue May 10 18:39:09 2011 +0000

    Use .cfi_sections to put the unwind info in .debug_frame when possible.
With
    this clang will use .debug_frame in, for example,
    clang -g -c -m32 test.c
    This matches gcc's behaviour. It looks like .debug_frame is a bit bigger
    than .eh_frame, but has the big advantage of not being allocated.

    git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@131140
91177308-0d34-0410-b5e6-96231b3b80d8

-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.



More information about the llvm-bugs mailing list