dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109524] "Invalid glsl version in shading_language_version()" when trying to run directX games using wine
Date: Thu, 04 Jul 2019 23:41:19 +0000	[thread overview]
Message-ID: <bug-109524-502-Tkd9Rb59Xu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109524-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1722 bytes --]

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

--- Comment #8 from Ilia Mirkin <imirkin@alum.mit.edu> ---
Doing a little more digging, we enabled GL_ARB_shading_language_100
unconditionally in 2013:

commit 70966570f3e4275dc15b5a94c70698f6aef64150
Author: Ian Romanick <ian.d.romanick@intel.com>
Date:   Thu Jun 27 18:20:31 2013 -0700

    mesa: GL_ARB_shading_language_100 is not optional

However it appears that wine code has something like

https://source.winehq.org/git/wine.git/blob/201d13a3c31131f204f89d61be37bf75d58dc6dd:/dlls/wined3d/adapter_gl.c#l3737

3737     if (gl_info->supported[ARB_SHADING_LANGUAGE_100])
3738     {
3739         const char *str = (const char
*)gl_info->gl_ops.gl.p_glGetString(GL_SHADING_LANGUAGE_VERSION_ARB);
3740         unsigned int major, minor;
3741 
3742         TRACE("GLSL version string: %s.\n", debugstr_a(str));
3743 
3744         /* The format of the GLSL version string is "major.minor[.release]
[vendor info]". */
3745         sscanf(str, "%u.%u", &major, &minor);
3746         gl_info->glsl_version = MAKEDWORD_VERSION(major, minor);

I think the debugstr_a(NULL) is giving problems, but if it's not, sscanf
probably will.

I'm not 100% sure who's right here. Certainly the GL_ARB_shading_language_100
spec talks about GL_SHADING_LANGUAGE_VERSION_ARB not being available due to it
not existing in early extension specs. 

However the current behavior is a bit questionable on the mesa side. I don't
know what the rationale was for always exposing the ext (as given, it's because
one ought to check for ARB_vertex_program/etc, but that seems weak).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2858 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-07-04 23:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 20:50 [Bug 109524] "Invalid glsl version in shading_language_version()" when trying to run directX games using wine bugzilla-daemon
2019-02-01  6:11 ` bugzilla-daemon
2019-05-04  2:33 ` bugzilla-daemon
2019-07-03  7:14 ` bugzilla-daemon
2019-07-03 16:43 ` bugzilla-daemon
2019-07-03 16:47 ` bugzilla-daemon
2019-07-03 17:11 ` bugzilla-daemon
2019-07-04 23:23 ` bugzilla-daemon
2019-07-04 23:41 ` bugzilla-daemon [this message]
2019-07-05  0:08 ` bugzilla-daemon
2019-07-05  5:15 ` bugzilla-daemon
2019-07-08 15:38 ` bugzilla-daemon
2019-07-09 18:57 ` bugzilla-daemon
2019-08-07 16:56 ` bugzilla-daemon
2019-08-07 16:57 ` bugzilla-daemon
2019-08-10 16:18 ` 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-109524-502-Tkd9Rb59Xu@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