From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99843] Geometry Shader - Incorrect Output
Date: Mon, 06 Nov 2017 20:09:30 +0000 [thread overview]
Message-ID: <bug-99843-502-mQmRDiAr8H@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99843-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 526 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99843
--- Comment #15 from dan@jerber.co.uk ---
I was reading about the R600 driver and came across a TODO page that suggested
testing using piglit.
I downloaded and compiled this. I ran the "shader.py" test and it gave the
following results:
skip: 26496 Pass: 6567 Warn: 2 Fail:496 Crash: 5
I'm not sure if piglit is a good measure on this but the number of fails seems
very high.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1262 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-11-06 20:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 20:24 [Bug 99843] Geometry Shader - Incorrect Output bugzilla-daemon
2017-02-16 21:13 ` bugzilla-daemon
2017-02-16 22:13 ` bugzilla-daemon
2017-02-16 22:16 ` bugzilla-daemon
2017-02-17 17:00 ` bugzilla-daemon
2017-02-17 17:01 ` bugzilla-daemon
2017-02-17 23:53 ` bugzilla-daemon
2017-02-17 23:55 ` bugzilla-daemon
2017-02-18 6:42 ` bugzilla-daemon
2017-02-18 11:38 ` bugzilla-daemon
2017-02-19 17:46 ` bugzilla-daemon
2017-06-22 17:07 ` bugzilla-daemon
2017-11-01 15:24 ` bugzilla-daemon
2017-11-01 15:30 ` bugzilla-daemon
2017-11-06 7:56 ` bugzilla-daemon
2017-11-06 10:10 ` bugzilla-daemon
2017-11-06 20:09 ` bugzilla-daemon [this message]
2019-09-18 19:22 ` 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-99843-502-mQmRDiAr8H@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.