From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103769] Unity based games do not start
Date: Fri, 17 Nov 2017 20:51:15 +0000 [thread overview]
Message-ID: <bug-103769-502-W209g8oGbM@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103769-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 409 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103769
--- Comment #3 from bartos.petr@gmail.com ---
For additional info, I've compiled latest mesa git with llvm 4.0 (stock version
of Fedora 26) and Unity games are working.
But I've no idea whether the problem is in llvm 6.0 itself, or how mesa is
using newest llvm library.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1138 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-11-17 20:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 18:06 [Bug 103769] Unity based games do not start bugzilla-daemon
2017-11-15 18:07 ` bugzilla-daemon
2017-11-15 18:07 ` bugzilla-daemon
2017-11-17 20:51 ` bugzilla-daemon [this message]
2017-11-27 10:27 ` bugzilla-daemon
2017-12-06 17:51 ` bugzilla-daemon
2017-12-06 19:25 ` bugzilla-daemon
2018-01-02 11:04 ` bugzilla-daemon
2018-01-02 20:18 ` bugzilla-daemon
2018-01-02 20:45 ` bugzilla-daemon
2018-01-02 20:45 ` bugzilla-daemon
2018-01-02 20:46 ` bugzilla-daemon
2018-04-02 10:50 ` bugzilla-daemon
2018-04-23 13:31 ` bugzilla-daemon
2018-04-23 13:35 ` bugzilla-daemon
2018-04-26 8:23 ` bugzilla-daemon
2019-09-12 6:43 ` bugzilla-daemon
2019-09-25 18:00 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-103769-502-W209g8oGbM@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).