From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66974] [radeonsi] rendering is broken in L4D2
Date: Thu, 15 Aug 2013 17:56:01 +0000 [thread overview]
Message-ID: <bug-66974-502-jfvLYDM70G@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66974-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 894 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66974
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Michel Dänzer <michel@daenzer.net> ---
commit b00269aa5887b88d2e037d6bfa374779902f8743
Author: Michel Dänzer <michel.daenzer@amd.com>
Date: Wed Aug 7 18:14:16 2013 +0200
radeonsi: Don't leave gaps between position exports from vertex shader
If the vertex shader exports clip distances but not point size, use
position exports 1/2 instead of 2/3 for the clip distances. Fixes
geometry corruption in that case.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2423 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
next prev parent reply other threads:[~2013-08-15 17:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 18:25 [Bug 66974] New: [radeonsi] rendering is broken in L4D2 bugzilla-daemon
2013-07-16 18:26 ` [Bug 66974] " bugzilla-daemon
2013-07-16 18:28 ` bugzilla-daemon
2013-07-19 13:54 ` bugzilla-daemon
2013-07-19 17:10 ` bugzilla-daemon
2013-07-19 17:12 ` bugzilla-daemon
2013-08-15 17:56 ` bugzilla-daemon [this message]
2013-08-17 16:55 ` bugzilla-daemon
2013-08-17 16:57 ` bugzilla-daemon
2013-08-17 17:01 ` bugzilla-daemon
2013-08-17 17:07 ` 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-66974-502-jfvLYDM70G@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).