dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 23 Dec 2010 08:51:05 -0800 (PST)	[thread overview]
Message-ID: <20101223165105.4439713004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-32544-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=32544

--- Comment #2 from Drill <drill87@gmail.com> 2010-12-23 08:51:05 PST ---
(In reply to comment #1)
> I don't have a problem with r300g/LLVM.
> 
> Could you possibly bisect the issue on your machine?

Unfortunately can't imagine how to do this at the moment.

The strange thing, is that i compile and use the old git version (from
15.11.2010) version in absolutely the same environment as the newest one git
version with the same options. But, as already mentioned, i'm getting on old
800 fps, and only 250 on new one :(

Forget to mention before - i'm using llvm 2.8 .

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-12-23 16:51 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 [this message]
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=20101223165105.4439713004E@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).