Bug ID | 1023614 |
---|---|
Summary | [LLVM] [AMDGPU] libllvm shader compiler creates invalid code |
Classification | openSUSE |
Product | openSUSE Distribution |
Version | Leap 42.2 |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | Kernel |
Assignee | kernel-maintainers@forge.provo.novell.com |
Reporter | f.thiessen@gmx.de |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
(Not sure if component Kernel is ok, but as it affects the userspace gpu compiler i thought it might fit). I dicovered some crashes of applications since the upgrade to 42.2 (from 42.1). E.g. the steam game "Airscape" crashes with this error: > Steam_SetMinidumpSteamID: Caching Steam ID: 76561198142264195 [API loaded no] > ATTENTION: default value of option force_s3tc_enable overridden by environment. > [17690:0204/180824:ERROR:sandbox_linux.cc(297)] InitializeSandbox() called with multiple threads in process gpu-process > LLVM triggered Diagnostic Handler: unsupported call to function exp10f in main > [17656:0204/180825:ERROR:breakpad_linux.cc(1226)] crash dump file written to /tmp/chromium-gpu-process-minidump-237b21943f4e8916.dmp > > file:///tmp/.org.chromium.Chromium.fKBPuJ/c2runtime.js:663 > var Dh=function(){function g(a){throw a;}function v(a){eval.call(null,a)}funct > ^ > TypeError: Cannot set property 'Dj' of null > at g.kg (file:///tmp/.org.chromium.Chromium.fKBPuJ/c2runtime.js:50:294) > at t.j7 (file:///tmp/.org.chromium.Chromium.fKBPuJ/c2runtime.js:94:329) > at t.Yq (file:///tmp/.org.chromium.Chromium.fKBPuJ/c2runtime.js:126:437) > at XMLHttpRequest.Zf.a.onload (file:///tmp/.org.chromium.Chromium.fKBPuJ/c2runtime.js:91:365) The interessting part and the part it has in common with the other crashes is: > LLVM triggered Diagnostic Handler: unsupported call to function exp10f in main I found out (thanks to the developer http://steamcommunity.com/app/317250/discussions/0/154644598513096190/ ) that this is caused by: https://bugs.freedesktop.org/show_bug.cgi?id=96495 https://reviews.llvm.org/D21282 So this is a bug in llvm < 3.9 and as Leap is using llvm 3.8 this affects Leap.