From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79338] Something's broken after llvm's svn commit 209067
Date: Wed, 28 May 2014 02:58:08 +0000 [thread overview]
Message-ID: <bug-79338-502-3yzd51kX7G@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-79338-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 824 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=79338
--- Comment #3 from Michel Dänzer <michel@daenzer.net> ---
(In reply to comment #3)
> [...] after a few minutes from launching a game (I have tried with CKII,
> Witcher 2, Watelands 2, Cities in motion, Deadfall Adventures and Serious Sam
> 3) or just after a few seconds after exiting the game [...]
If you capture an apitrace of one of those games, does the problem also occur
after replaying the apitrace?
> I am using a llvm ppa to install llvm 3.5 git.
Do the ppa packages use any patches versus upstream?
> I've tried to compile llvm with no luck, so I cannot bisect.
What's the problem compiling LLVM? It would probably be best if you could
bisect yourself.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1756 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-05-28 2:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 23:21 [Bug 79338] New: Something's broken after llvm's svn commit 209067 bugzilla-daemon
2014-05-27 23:36 ` [Bug 79338] " bugzilla-daemon
2014-05-27 23:37 ` bugzilla-daemon
2014-05-28 2:58 ` bugzilla-daemon [this message]
2014-05-28 10:09 ` bugzilla-daemon
2014-05-29 8:19 ` bugzilla-daemon
2014-05-29 21:22 ` bugzilla-daemon
2014-05-29 21:33 ` bugzilla-daemon
2014-05-29 22:22 ` 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-79338-502-3yzd51kX7G@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