From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31635] [r300g]Bad performance of 64-bit compilation compared to 32-bit.
Date: Mon, 15 Nov 2010 11:15:44 -0800 (PST) [thread overview]
Message-ID: <20101115191545.26DF913004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-31635-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=31635
Drill <drill87@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Bad performance of 64-bit |[r300g]Bad performance of
|compilation compared to |64-bit compilation compared
|32-bit. |to 32-bit.
--
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:[~2010-11-15 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 19:03 [Bug 31635] New: Bad performance of 64-bit compilation compared to 32-bit bugzilla-daemon
2010-11-15 19:15 ` bugzilla-daemon [this message]
2010-11-15 20:51 ` [Bug 31635] [r300g]Bad " bugzilla-daemon
2010-11-15 21:16 ` bugzilla-daemon
2010-11-16 7:46 ` bugzilla-daemon
2010-11-16 7:47 ` 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=20101115191545.26DF913004E@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