All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62696] [r300g, bisected] Around 50 piglit vs variable-indexing tests fails after "glsl_to_tgsi: allocate arrays separately v2"
Date: Mon, 25 Mar 2013 08:51:34 +0000	[thread overview]
Message-ID: <bug-62696-502-u7mzxmXsg2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-62696-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1503 bytes --]

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

Christian König <deathsimple@vodafone.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #5 from Christian König <deathsimple@vodafone.de> ---
(In reply to comment #4)
> I thought the array support was backward compatible. If if were true, this
> patch wouldn't be needed, right?

Yes indeed, and I find that rather strange, too.

Well one thing that I haven't considered before is that when a target doesn't
support indirect addressing all indirect accesses are replaced with a chain of
"if (i == 0) then return x[0] else if (i == 1) then return x[1].....", so
having arrays separated makes this inefficient code even more inefficient
(cause the register scavenger then leaves arrays alone), that's what this patch
really should fix.

But you're right, it should NEVER result in incorrect code, so we either have a
bug in R300g that's triggered by using more registers than necessary
(unlikely), or we are still missing something in the glsl_to_tgsi pass
(likely).

@Pavel: Could you make sure that the vs-uniform-array-mat2-col-row-rd test is
indeed failing with that change? And also please attach a log of the good case
for this test.

Thanks in advance,
Christian.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3199 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-03-25  8:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24 13:36 [Bug 62696] New: [r300g, bisected] Around 50 piglit vs variable-indexing tests fails after "glsl_to_tgsi: allocate arrays separately v2" bugzilla-daemon
2013-03-24 13:37 ` [Bug 62696] " bugzilla-daemon
2013-03-24 15:27 ` bugzilla-daemon
2013-03-24 17:28 ` bugzilla-daemon
2013-03-24 20:03 ` bugzilla-daemon
2013-03-25  8:51 ` bugzilla-daemon [this message]
2013-03-25 10:03 ` bugzilla-daemon
2013-03-25 12:54 ` bugzilla-daemon
2013-03-26 10:39 ` 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=bug-62696-502-u7mzxmXsg2@http.bugs.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 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.