From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66713] Team Fortress 2 crashes with r600-sb on HD4850
Date: Sat, 13 Jul 2013 23:07:32 +0000 [thread overview]
Message-ID: <bug-66713-502-SyS3c2pRLg@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66713-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 648 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66713
--- Comment #5 from Vadim Girlin <ptpzz@yandex.ru> ---
You didn't mention llvm backend so I tried without it. Now I see some problems,
but so far for me it looks not really sb-related. I'll try to sort it out,
though I don't think that using llvm and sb together makes a lot of sense -
they are basically trying to do the same things so it's just a duplication of
work. Also such configuration is less tested than llvm backend or sb alone, so
you might want to use only one of them (at least until this issue is fixed).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1411 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:[~2013-07-13 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 21:45 [Bug 66713] New: Team Fortress 2 crashes with r600-sb on HD4850 bugzilla-daemon
2013-07-08 21:54 ` [Bug 66713] " bugzilla-daemon
2013-07-09 23:42 ` bugzilla-daemon
2013-07-13 11:00 ` bugzilla-daemon
2013-07-13 13:23 ` bugzilla-daemon
2013-07-13 23:07 ` bugzilla-daemon [this message]
2013-07-14 2:40 ` bugzilla-daemon
2013-07-17 14:49 ` bugzilla-daemon
2013-07-28 13:05 ` 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-66713-502-SyS3c2pRLg@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).