All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 46006] New: [r300g, bisected] piglit glsl-max-varyings fails
Date: Mon, 13 Feb 2012 19:21:28 +0000	[thread overview]
Message-ID: <bug-46006-502@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 46006
           Summary: [r300g, bisected] piglit glsl-max-varyings fails
    Classification: Unclassified
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Keywords: regression
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: pavel.ondracka@email.cz
                CC: maraeo@gmail.com


This is the last r300g piglit regression from 7.11 to 8.0. I'm not sure if this is a valid bug, there is lots of errors:

r300: ERROR: FS input generic 20 unassigned, not enough hardware slots (it's not a bug, do not report it).
r300: ERROR: FS input generic 21 unassigned, not enough hardware slots (it's not a bug, do not report it).

However since this is a regression I'm reporting it nevertheless. May also be related to bug 34201 


Output:
Vertical axis: Increasing numbers of varyings.
Horizontal axis: Which of the varyings contains the color.
GL_MAX_VARYING_FLOATS = 40
Probe at (8,98)
  Expected: 0.000000 1.000000 0.000000
  Observed: 0.000000 0.000000 0.000000
  Failure with 9 vec4 varyings used in varying index 0
Probe at (8,110)
  Expected: 0.000000 1.000000 0.000000
  Observed: 0.000000 0.000000 0.000000
  Failure with 10 vec4 varyings used in varying index 0


1ded658ce074a85bc08c989ff17840b840ff3051 is the first bad commit
commit 1ded658ce074a85bc08c989ff17840b840ff3051
Author: Marek Olšák <maraeo@gmail.com>
Date:   Tue Nov 22 15:05:29 2011 +0100

    st/mesa: add color varyings to MaxVarying

    The linker now adds color varyings to the number of used varyings and checks
    against that limit.

    NOTE: This is a candidate for the 7.11 branch.


GPU: RV530
Mesa: df1cd55ebf362948788c04d2fa7da55c80991605
Kernel: 3.2.3
Libdrm: 2.4.31

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2012-02-13 19:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13 19:21 bugzilla-daemon [this message]
2013-02-08 11:40 ` [Bug 46006] [r300g, bisected] piglit glsl-max-varyings fails 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-46006-502@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.