From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63579] Savage 2 Edges render white [r600g]
Date: Tue, 16 Apr 2013 19:06:55 +0000 [thread overview]
Message-ID: <bug-63579-502-B0lqAnGHmH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-63579-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1777 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63579
--- Comment #9 from Erik Faye-Lund <kusmabite@gmail.com> ---
I don't know where you have the retroactive-story from, but the specification
does not mention it being retroactive, and even goes as far as to say:
"This document specifies only version 4.20 of the OpenGL Shading Language. It
requires __VERSION__ to substitute 420, and requires #version to accept only
420. If #version is declared with a smaller number, the language accepted is a
previous version of the shading language, which will be supported depending on
the version and type of context in the OpenGL API. See the OpenGL Graphics
System Specification, Version 4.2, for details on what language versions are
supported. Previous versions of the OpenGL Shading Language, as well as the
OpenGL ES Shading Language, are not strict subsets of the version specified
here, particularly with respect to precision, name-hiding rules, and treatment
of interface variables. See the specification corresponding to a particular
language version for details specific to that version of the language."
And new revisions of those older shader-languages specifications have not been
issued. You are right in saying that the specs allows for comments before the
#version-string, but IMO the only reasonable thing to do in such a case is to
not support line-continuation characters until a version declaration has been
defined.
As for what "every other vendor has implemented line continuation in some form
since forever", I can tell you that at least my NVIDIA OpenGL 4.3 driver does
*not* implement line continuation, seemingly in *any* form. Not even when the
shader starts with "#version 420".
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2554 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-04-16 19:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 0:56 [Bug 63579] New: Savage 2 Edges render white [r600g] bugzilla-daemon
2013-04-16 0:57 ` [Bug 63579] " bugzilla-daemon
2013-04-16 0:58 ` bugzilla-daemon
2013-04-16 0:59 ` bugzilla-daemon
2013-04-16 2:11 ` bugzilla-daemon
2013-04-16 3:04 ` bugzilla-daemon
2013-04-16 3:37 ` bugzilla-daemon
2013-04-16 3:43 ` bugzilla-daemon
2013-04-16 4:37 ` bugzilla-daemon
2013-04-16 7:20 ` bugzilla-daemon
2013-04-16 17:25 ` bugzilla-daemon
2013-04-16 19:06 ` bugzilla-daemon [this message]
2013-04-17 8:32 ` bugzilla-daemon
2013-04-17 17:03 ` bugzilla-daemon
2013-04-17 17:10 ` bugzilla-daemon
2013-04-17 18:13 ` bugzilla-daemon
2013-04-17 18:51 ` bugzilla-daemon
2013-04-17 20:03 ` bugzilla-daemon
2013-04-17 20:52 ` bugzilla-daemon
2013-04-17 21:19 ` bugzilla-daemon
2013-04-17 21:38 ` bugzilla-daemon
2013-05-18 2:41 ` bugzilla-daemon
2013-05-18 12:37 ` bugzilla-daemon
2019-09-18 19:02 ` 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-63579-502-B0lqAnGHmH@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