[LLVMbugs] [Bug 11785] New: llvm linker fails to link code because of a type problem. caused by revision 146932

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Tue Jan 17 06:19:15 PST 2012


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

             Bug #: 11785
           Summary: llvm linker fails to link code because of a type
                    problem. caused by revision 146932
           Product: libraries
           Version: trunk
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: Linker
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: hkultala at cs.tut.fi
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified


Created attachment 7895
  --> http://llvm.org/bugs/attachment.cgi?id=7895
tarball containg bytecode files whoose linkage fails.

This code links correctly with llvm-svn revision 146931.

But with revision 146932 this breaks.

the .o files in the tarball are bitcode files, and .a files are ar achive
containing bitcode files

how to reproduce:

unpack the tar.bz2 package, go to the directory, run:

llvm-ld -disable-opt *.o *.a -o foo





The error message is:

Load result type does not match pointer operand type!
  %6 = load %0** getelementptr inbounds ([258 x %0*]* @__malloc_av_, i32 0, i32
2), align 4, !tbaa !3



My guess is that the type mapping changes in r146932 are incomplete;

it seems that many types with same name are mapped together to be same type,
but when they are structs containing structs, those "inner structs" are not
mapped together correctly and then the types look different even they are the
same.

-- 
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