[LLVMbugs] [Bug 24222] New: compiler-rt cmake configure fails on 32-bit systems

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Wed Jul 22 14:10:35 PDT 2015


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

            Bug ID: 24222
           Summary: compiler-rt cmake configure fails on 32-bit systems
           Product: new-bugs
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: new bugs
          Assignee: unassignedbugs at nondot.org
          Reporter: hans at chromium.org
                CC: llvmbugs at cs.uiuc.edu, popizdeh at gmail.com,
                    samsonov at google.com
            Blocks: 24126
    Classification: Unclassified

Nikola reports failing to configure compiler-rt on 32-bit OpenSUSE and Fedora
with CMake.

On Fedora, gcc targets i686 so the first stage (building compiler-rt and clang)
of a bootstrap build succeeds.

But the second stage (building with the newly built clang) fails, because Clang
does not define __i686__.

clang --version says it targets i686-pc-linux-gnu, but it doesn't define
__i686__.

On my regular x86_64 workstation, it doesn't work either:

$ bin/clang -target i686-pc-linux-gnu -v
Prints "Target: i686-pc-linux-gnu" as expected, but:
$ bin/clang -target i686-pc-linux-gnu -dM -E -c /tmp/a.c | grep i.*86
Only prints __i386__, __i386 and i386.

Isn't Clang supposed to define __i686__ when targeting i686? Am I holding it
wrong? Is compiler-rt checking the wrong thing?



On OpenSUSE, even Phase1 fails, because the system gcc is targeting i586
instead of i686:
gcc -v prints i586-suse-linux. It defines __i386__ and __i586__.
I suppose that's a different kind of bug, but it also seems related.

I have VMs for 32-bit OpenSUSE and Fedora set up. Let me know if I can help
debugging.

-- 
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/20150722/0f1a9051/attachment.html>


More information about the llvm-bugs mailing list