From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32544] [r300g] LLVM support for software TLS implementation doesn't work
Date: Tue, 4 Jan 2011 08:24:45 -0800 (PST) [thread overview]
Message-ID: <20110104162446.2456B13004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-32544-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=32544
Brian Paul <brianp@vmware.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #8 from Brian Paul <brianp@vmware.com> 2011-01-04 08:24:46 PST ---
I think the first patch is actually the better one. It lets all drivers that
utilize the draw module to get LLVM acceleration when LLVM is present and
avoids having LLVM code in each of the drivers.
If there's no objections, I'll revert commit
88550083b3857184445075e70fed8b2eed4952a1 and apply the first attached patch.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-01-04 16:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 7:20 [Bug 32544] New: [r300g] LLVM support for software TLS implementation doesn't work bugzilla-daemon
2010-12-22 18:22 ` [Bug 32544] " bugzilla-daemon
2010-12-23 16:51 ` bugzilla-daemon
2010-12-24 9:37 ` bugzilla-daemon
2010-12-24 9:39 ` bugzilla-daemon
2010-12-24 15:28 ` bugzilla-daemon
2010-12-24 16:55 ` bugzilla-daemon
2010-12-24 17:40 ` bugzilla-daemon
2011-01-04 16:24 ` bugzilla-daemon [this message]
2011-01-04 16:44 ` bugzilla-daemon
2011-01-04 16:47 ` bugzilla-daemon
2011-01-24 10:54 ` 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=20110104162446.2456B13004E@annarchy.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).