Bug 15136 - glCompileShaderARB set OBJECT_COMPILE_STATUS_ARB false after call glAttachObjectARB
Summary: glCompileShaderARB set OBJECT_COMPILE_STATUS_ARB false after call glAttachObj...
Status: VERIFIED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: lowest trivial
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-19 22:57 UTC by WuNian
Modified: 2009-08-24 12:29 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
test case (2.00 KB, text/plain)
2008-03-19 22:57 UTC, WuNian
Details

Description WuNian 2008-03-19 22:57:57 UTC
Created attachment 15327 [details]
test case

If call glAttachObjectARB firstly, then call glCompileShaderARB, the OBJECT_COMPILE_STATUS_ARB will be set as GL_FALSE, following is the code fragment:

shader = glCreateShaderObjectARB(GL_FRAGMENT_SHADER_ARB);
   glShaderSourceARB(shader, 1, shaderSrc, NULL);
   program = glCreateProgramObjectARB();
   glAttachObjectARB(program, shader);
   glCompileShaderARB(shader);
   glGetObjectParameterivARB(shader, GL_OBJECT_COMPILE_STATUS_ARB, &compiled);

With soft rendering, there is no this issue.
With OpenGL2.0 function call, there is no this issue.
Comment 1 Zou Nan hai 2008-03-23 22:23:37 UTC
soft rendering case is not correct here.
Please reassign the bug to mesa core
Comment 2 WuNian 2008-03-24 18:46:20 UTC
(In reply to comment #1)
> soft rendering case is not correct here.
> Please reassign the bug to mesa core
Soft rendering is OK. Indirect rendering is also incorrect.
As you said, Mesa core is responsible for the shader compilation, assign the bug to Mesa core.

Comment 3 Shuang He 2009-06-03 18:57:57 UTC
This issue has gone
Comment 4 Shuang He 2009-06-03 18:58:14 UTC
verified against:
mesa: (master)0e8a5a84742adf6e99236f246c77325fad174204
Comment 5 Adam Jackson 2009-08-24 12:29:40 UTC
Mass version move, cvs -> git


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.