From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 32544] New: [r300g] LLVM support for software TLS implementation doesn't work
Date: Mon, 20 Dec 2010 23:20:12 -0800 (PST) [thread overview]
Message-ID: <bug-32544-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=32544
Summary: [r300g] LLVM support for software TLS implementation
doesn't work
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: drill87@gmail.com
Hello. A month ago I started to use --enable-gallium-llvm while compiling mesa
git version and got a great performance increase - glxgears showed 800 fps vs
250 without LLVM.
But in newer git versions (starting from the end of November or so) this
option stopped to help me - I've got 250 fps both with --enable-gallium-llvm
and without today.
So is LLVM support (as I understood) for TLS implementation working in r300g?
Or the problem only on my side...
Kernel: 2.6.36 x86-64 (Archlinux 64)
Videocard: ATI Radeon X1270 (RS690)
--
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:[~2010-12-21 7:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 7:20 bugzilla-daemon [this message]
2010-12-22 18:22 ` [Bug 32544] [r300g] LLVM support for software TLS implementation doesn't work 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
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=bug-32544-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.