[llvm-bugs] [Bug 35678] New: clang segfaults compiling gzip (and probably others) when using -march=native on Core2 Duo (penryn)

via llvm-bugs llvm-bugs at lists.llvm.org
Sun Dec 17 05:01:32 PST 2017


            Bug ID: 35678
           Summary: clang segfaults compiling gzip (and probably others)
                    when using -march=native on Core2 Duo (penryn)
           Product: clang
           Version: 5.0
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: moralapostel at gmail.com
                CC: llvm-bugs at lists.llvm.org

Distro: Gentoo

Reproducilibility: Always

Affected Clang versions: 5.0.0 and 5.0.1_rc2

Expected result: No segfaults

Actual result:


clang-5.0: error: unable to execute command: Segmentation fault
clang-5.0: error: clang frontend command failed due to signal (use -v to see
clang version 5.0.1 (tags/RELEASE_501/rc2)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
clang-5.0: note: diagnostic msg: PLEASE submit a bug report to  and include the
crash backtrace, preprocessed source, and associated run script.
clang-5.0: note: diagnostic msg: Error generating preprocessed source(s) - no
preprocessable inputs.


I will attach the full build log below.

Workaround: Specifying -mno-sse4.1 eliminates the segfault, even though this
CPU supports SSE 4.1

Is clang maybe trying to use some other SSE instructions that aren't available
on this old-ish CPU?

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/20171217/61cff8a0/attachment.html>

More information about the llvm-bugs mailing list