From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74717] r600g: 'invalid read' linking geometry shader
Date: Sun, 09 Feb 2014 14:08:24 +0000 [thread overview]
Message-ID: <bug-74717-502-QMvbk6g4PD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-74717-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 811 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=74717
--- Comment #5 from Török Edwin <edwin+mesa@etorok.net> ---
(In reply to comment #4)
> (In reply to comment #3)
> > G-truck samples don't work for me too (similar error for ether samples):
> >
> > ./gl-320-primitive-shading
> > OpenGL Version Needed 3.2 ( 3.3 Found )
> > Shader Compiler: error(high) 2: 0:1(1): error: syntax error, unexpected $end
> > Shader Compiler: error(high) 3: 0:1(1): error: syntax error, unexpected $end
> > Shader Compiler: error(high) 4: 0:1(1): error: syntax error, unexpected $end
>
> You need to run it from the source root, like this:
> $ build/build/release/gl-320-primitive-shading
build/release/gl-320-primitive-shading
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1759 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:[~2014-02-09 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 17:49 [Bug 74717] New: r600g: 'invalid read' linking geometry shader bugzilla-daemon
2014-02-08 19:32 ` [Bug 74717] " bugzilla-daemon
2014-02-08 22:03 ` bugzilla-daemon
2014-02-09 13:33 ` bugzilla-daemon
2014-02-09 14:05 ` bugzilla-daemon
2014-02-09 14:08 ` bugzilla-daemon [this message]
2014-02-09 14:55 ` bugzilla-daemon
2014-02-10 8:12 ` 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-74717-502-QMvbk6g4PD@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