From: Brian Paul <brianp@vmware.com>
To: Conn Clark <conn.o.clark@gmail.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: Possible fix to _mesa_remove_extra_moves function in shader/prog_optimize.c (request testing)
Date: Thu, 06 May 2010 15:50:41 -0600 [thread overview]
Message-ID: <4BE339B1.5020507@vmware.com> (raw)
In-Reply-To: <k2m1d724411005051335z2d4a69b8kc0af7878900cbb4e@mail.gmail.com>
Conn Clark wrote:
> Hello,
>
> Here is a possible fix/hack to get _mesa_remove_extra_moves function
> in shader/prog_optimize.c usable. As far as I could tell with my
> testing there was an issue with this optimizing pass and OPCODE_MUL .
> I just added an exception to for this one instruction and made it easy
> to add others should further testing indicate they need to be added
> too.
>
> It bumped my Nexuiz scores on demo1 from 5,8,and 12 to 5,9, and 13. It
> also reduced the testing runtime from 234 seconds to 225 seconds.
>
>
> I have only tested on my radeon hd 3100 based laptop but would like to
> hear results from other types of cards too.
I'm a bit nervous about enabling that function without a _lot_ more
testing. And any special case added for MUL would seem to apply to
any ALU instruction. That tells me that there's probably other issues
to shake out of the code before we can enable it.
If you're interested, you should at least run the glean and piglits
tests which exercise shaders and GPU programs.
-Brian
next prev parent reply other threads:[~2010-05-06 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 20:35 Possible fix to _mesa_remove_extra_moves function in shader/prog_optimize.c (request testing) Conn Clark
2010-05-06 21:50 ` Brian Paul [this message]
2010-05-06 22:27 ` Conn Clark
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=4BE339B1.5020507@vmware.com \
--to=brianp@vmware.com \
--cc=conn.o.clark@gmail.com \
--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.