[Mesa-dev] XOrg EVoC - Piglit tests for ARB_gpu_shader5 and ARB_tessellation_shader

[Ken Phillis Jr]

Hi, I am looking to enter the Xorg EVoC for 2012, and am wanting to Implement
two Core extensions for OpenGL 4.0 and GLSL 4.00.


------------------------------------------------------------------------
Name:
	Piglit - Implement Tessellation shaders Extension Tests

Summary:
	To implement the initial Tessellation shader support into the Piglit testing
	framework. This will be done using extensions to OpenGL 3.2, and GLSL 1.50.
	These extensions are called ARB_tessellation_shader, and ARB_gpu_shader5.

Description:
	I would like to start off by studying the Piglit code base, and looking at
	what changes are required so that the OpenGL 3.20, and GLSL 1.50 overall
	requirements for these extensions are met. If there is no major problems
	with the current framework, I'll start Implementing the numerous tests of
	ARB_tessellation_shader. Once I finish Implementing the tests for this
	extension, I will move on to the ARB_gpu_shader5 extension, and Implement
	the core of this extension. Once both Extensions are finished, I will start
	implementation of the Interaction tests with other extensions.
	
	At the end of each Stage I will submit a review of All the code written up
	to that point, and Improve the overall readability. This includes adding
	documentation, and comments where Features are added and/or modified.

Benefits:
	The community as a whole will have an Open Source tool to test the overall
	conformance to the specifications for the extensions ARB_gpu_shader5 and
	ARB_tessellation_shader. These two extensions are core features found in
	OpenGL 4.0, and GLSL 4.0.

Schedule:
	I plan on working on this project full time for 10 to 14 weeks, and then
	continue working on this project for another 2 to 4 weeks part time
	improving documentation and code readability.
		*Week 1: Study the Specifications and Piglit's Design, and Start
			implementing the Missing features that will prevent general testing
			of these two extensions. If no Changes are required, the
			Implementation of ARB_tessellation_shader will start.

		*Week 2-4: Continue Implementing the tests and Utilities for the
			extension ARB_tessellation_shader.

		*Week 5: Submit the ARB_tessellation_shader source for Code Review, and
			begin Implementing ARB_gpu_shader5 Utilities and tests.

		*Week 6-7: Continue the ARB_gpu_shader5 Implementation.
		
		*Week 8: Submit ARB_gpu_shader5 sources for Code Review, and then begin
			Implementing the code review changes for ARB_tessellation_shader.
			
		*Week 9: Continue Implementing code review Changes, and begin work on
			ARB_gpu_shader5, and ARB_tessellation_shader interactions.
		
		*Week 10-12: Continue Implementation of Interactions, and Apply
			changes suggested in code review.
		*Week 13+: Submit Code for Final Review Once Again, and apply fixes.
			
Note: If I wind up ahead of schedule for Any reason, I will take the time to
	implement ARB_gpu_shader_fp64 and it's Interactions.
------------------------------------------------------------------------