From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37603] New: r600g with LLVM enabled makes Heroes of Newerth game unplayable
Date: Wed, 25 May 2011 14:36:34 -0700 (PDT) [thread overview]
Message-ID: <bug-37603-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=37603
Summary: r600g with LLVM enabled makes Heroes of Newerth game
unplayable
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: damien@grassart.com
Created an attachment (id=47162)
--> (https://bugs.freedesktop.org/attachment.cgi?id=47162)
Blurry loading screen
Hi, recent versions of Mesa have made this game go from 30 fps down to under 1
fps, and have caused the bottom of textures to become blurry (see attachment).
I've bisected it down to commit a86fc719d6402eb482657707741890e69e81700f
(enable LLVM by default on x86 and x86_64). I don't know why LLVM causes this
but I've verified that disabling it via configure fixes this problem. I now
use:
./configure --prefix=$HOME --enable-gallium-r600 --disable-gallium-r300
--disable-gallium-llvm --disable-gallium-egl --with-state-trackers=dri
I know r300g requires LLVM but are there any reasons to enable it for r600g?
Thanks,
-Damien
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-05-25 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 21:36 bugzilla-daemon [this message]
2011-05-26 5:50 ` [Bug 37603] r600g with LLVM enabled makes Heroes of Newerth game unplayable bugzilla-daemon
2011-05-26 6:13 ` bugzilla-daemon
2011-05-26 12:03 ` 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-37603-502@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