From: Brian Paul <brianp@vmware.com>
To: Luca Barbieri <luca@luca-barbieri.com>
Cc: "nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"mesa3d-dev@lists.sourceforge.net"
<mesa3d-dev@lists.sourceforge.net>
Subject: Re: [PATCH 2/2] st: don't assert on empty fragment program
Date: Mon, 18 Jan 2010 11:01:44 -0700 [thread overview]
Message-ID: <4B54A208.10803@vmware.com> (raw)
In-Reply-To: <1263764160-8891-2-git-send-email-luca@luca-barbieri.com>
Luca Barbieri wrote:
> Sauerbraten triggers this assert.
> ---
> src/mesa/state_tracker/st_atom_shader.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/src/mesa/state_tracker/st_atom_shader.c b/src/mesa/state_tracker/st_atom_shader.c
> index 176f3ea..fce533a 100644
> --- a/src/mesa/state_tracker/st_atom_shader.c
> +++ b/src/mesa/state_tracker/st_atom_shader.c
> @@ -79,8 +79,6 @@ translate_fp(struct st_context *st,
>
> stfp->num_input_slots = numIn;
>
> - assert(stfp->Base.Base.NumInstructions > 1);
> -
> st_translate_fragment_program(st, stfp, stfp->input_to_slot);
> }
> }
How do we end up with a shader that has only one instruction (or
none)? Is it an END instruction? I'd like to learn more about what's
happening before committing this.
-Brian
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
next prev parent reply other threads:[~2010-01-18 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 21:35 [PATCH 1/2] nv40: don't crash on empty fragment program Luca Barbieri
[not found] ` <1263764160-8891-1-git-send-email-luca-Ukmtq+NC3rhBHFWNQifrYwC/G2K4zDHf@public.gmane.org>
2010-01-17 21:36 ` [PATCH 2/2] st: don't assert " Luca Barbieri
2010-01-18 18:01 ` Brian Paul [this message]
[not found] ` <4B54A208.10803-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2010-01-18 18:15 ` [Mesa3d-dev] " Luca Barbieri
2010-01-18 18:26 ` Brian Paul
[not found] ` <4B54A7C6.4060402-pghWNbHTmq7QT0dZR+AlfA@public.gmane.org>
2010-01-18 18:30 ` [Mesa3d-dev] " Luca Barbieri
2010-01-18 18:27 ` Roland Scheidegger
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=4B54A208.10803@vmware.com \
--to=brianp@vmware.com \
--cc=luca@luca-barbieri.com \
--cc=mesa3d-dev@lists.sourceforge.net \
--cc=nouveau@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.