From: Shuang He <shuang.he@intel.com>
To: "Kristian Høgsberg" <krh@kemper.freedesktop.org>,
"Graunke, Kenneth W" <kenneth.w.graunke@intel.com>
Cc: "mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>,
intel-gfx@lists.freedesktop.org
Subject: Re: Mesa (master): i965: Don't write mrf assignment for pointsize output
Date: Fri, 26 Nov 2010 08:37:25 +0800 [thread overview]
Message-ID: <4CEF0145.7060103@intel.com> (raw)
In-Reply-To: <20101124162943.BDD8C10057@kemper.freedesktop.org>
For you information:
This commit fixes 17 OpenGL ES 2.0 conformance cases on i965
And also another 1 commit from Ken also fixes 1 case
So We have 18 more passes on OpenGL ES 2.0 conformance on i965 these two
days
Thanks
--Shuang
On 2010-11-25 0:29, Kristian Høgsberg wrote:
> Module: Mesa
> Branch: master
> Commit: a889f9ee5cccee031c1090a6ef92cba894b1d77c
> URL: http://cgit.freedesktop.org/mesa/mesa/commit/?id=a889f9ee5cccee031c1090a6ef92cba894b1d77c
>
> Author: Kristian Høgsberg<krh@bitplanet.net>
> Date: Wed Nov 24 10:12:20 2010 -0500
>
> i965: Don't write mrf assignment for pointsize output
>
> https://bugs.freedesktop.org/show_bug.cgi?id=31894
>
> ---
>
> src/mesa/drivers/dri/i965/brw_vs_emit.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/src/mesa/drivers/dri/i965/brw_vs_emit.c b/src/mesa/drivers/dri/i965/brw_vs_emit.c
> index a13c3ca..89e4caf 100644
> --- a/src/mesa/drivers/dri/i965/brw_vs_emit.c
> +++ b/src/mesa/drivers/dri/i965/brw_vs_emit.c
> @@ -281,7 +281,6 @@ static void brw_vs_alloc_regs( struct brw_vs_compile *c )
> else if (i == VERT_RESULT_PSIZ) {
> c->regs[PROGRAM_OUTPUT][i] = brw_vec8_grf(reg, 0);
> reg++;
> - mrf++; /* just a placeholder? XXX fix later stages& remove this */
> }
> else {
> /* Two restrictions on our compute-to-MRF here. The
> @@ -1603,6 +1602,8 @@ static void emit_vertex_write( struct brw_vs_compile *c)
> break;
> if (!(c->prog_data.outputs_written& BITFIELD64_BIT(i)))
> continue;
> + if (i == VERT_RESULT_PSIZ)
> + continue;
>
> if (i>= VERT_RESULT_TEX0&&
> c->regs[PROGRAM_OUTPUT][i].file == BRW_GENERAL_REGISTER_FILE) {
>
> _______________________________________________
> mesa-commit mailing list
> mesa-commit@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/mesa-commit
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
parent reply other threads:[~2010-11-26 0:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20101124162943.BDD8C10057@kemper.freedesktop.org>]
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=4CEF0145.7060103@intel.com \
--to=shuang.he@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kenneth.w.graunke@intel.com \
--cc=krh@kemper.freedesktop.org \
--cc=mesa-dev@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.