Bug 100104 - Gallium-9 hitting LLVM assert when trying to start EVE-Online
Summary: Gallium-9 hitting LLVM assert when trying to start EVE-Online
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/radeonsi (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact: Default DRI bug account
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-07 17:41 UTC by Mathieu Belanger
Modified: 2018-04-03 05:39 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Mathieu Belanger 2017-03-07 17:41:19 UTC
Hi,
EVE-Online don't start anymore since I upgraded to last Mesa GIT and LLVM git two days ago. The game start, Like you see the black screen and the login loading bar and then it crash with that error.

void llvm::LiveRangeEdit::eliminateDeadDef(llvm::MachineInstr*, llvm::LiveRangeEdit::ToShrinkSet&, llvm::AliasAnalysis*): Assertion `MI->allDefsAreDead() && "Def isn't really dead"' failed.

From the LLVM bugs, It got reported last years but nothing append because "this path is not used by default"

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

I don't know if it's the same and/or if I have to post that on the llvm bugs (waiting for a login as they allow people to register on there bugzilla).

Note : It do work (but unplayable in 4K) without Gallium-9.
Comment 1 Michel Dänzer 2017-03-08 01:48:02 UTC
Can you check if it's due to Mesa or LLVM, then bisect the one that triggered it?
Comment 2 Mathieu Belanger 2017-03-09 04:04:39 UTC
Work fine with LLVM4-rc3 ang mesa git so I assume the but is in LLVM.

Where do I post LLVM bisect if I do it as I did not yet get a response for manually subscribe to the bugzilla?
Comment 3 Michel Dänzer 2017-03-09 06:17:23 UTC
Here is fine.
Comment 4 Timothy Arceri 2018-04-03 05:39:51 UTC
Closing as per upsteam bug.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.