[llvm-bugs] [Bug 39720] New: "Illegal instruction" after successful building of ungoogled-chromium
    via llvm-bugs 
    llvm-bugs at lists.llvm.org
       
    Tue Nov 20 06:08:39 PST 2018
    
    
  
https://bugs.llvm.org/show_bug.cgi?id=39720
            Bug ID: 39720
           Summary: "Illegal instruction" after successful building of
                    ungoogled-chromium
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: release blocker
          Priority: P
         Component: Backend: X86
          Assignee: unassignedbugs at nondot.org
          Reporter: studio at anchev.net
                CC: craig.topper at gmail.com, llvm-bugs at lists.llvm.org,
                    llvm-dev at redking.me.uk, spatel+llvm at rotateright.com
Created attachment 21133
  --> https://bugs.llvm.org/attachment.cgi?id=21133&action=edit
cat /proc/cpuinfo
STR:
1. Build LLVM from SVN source code using the following script:
https://susepaste.org/c1b26468
2. Build ungoogled-chromium using this script:
https://susepaste.org/01f12c78
3. Execute the final binary /opt/ungoogled-chromium/chrome
EXPECTED:
The program should start normally.
ACTUAL:
An error message about "Illegal instruction" is displayed and the program
doesn't start.
[~]: /opt/ungoogled-chromium/chrome
Illegal instruction (core dumped)
[~]: [8940:8940:1120/151713.340872:ERROR:sandbox_linux.cc(379)]
InitializeSandbox() called with multiple threads in process gpu-process.
Using an older LLVM build (trunk 346299) which was also generated through step
1 does not give "Illegal instruction" and chrome works fine.
Additional note:
The second error about sandbox is unrelated to this bug and is displayed even
chrome is built with the good version of LLVM (trunk 346299). The first trunk
in which I noticed this problem was 346584. Reported also to
ungoogled-chromium:
https://github.com/Eloston/ungoogled-chromium/issues/586
Attaching /proc/cpuinfo.
-- 
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/20181120/a956e093/attachment.html>
    
    
More information about the llvm-bugs
mailing list