util: Fix rgb9e5's big-endian test

__BIG_ENDIAN__ is predefined by gcc at least, MESA_BIG_ENDIAN isn't
defined anywhere in piglit though.

Signed-off-by: Adam Jackson <ajax@redhat.com>
Apply the same local fix to enum.spec that we did for enumext.spec.
Include enum.spec along with enumext.spec for piglit-dispatch.

There are three differences between the two (as verified by sort, sed,
uniq, and diff):

- enum.spec includes GLES extension enums (since it's used for
  maintaining uniqueness of enums in the registry), which we want to
  include for cross-API compatibility.
- enum.spec includes some entries for known GL versions and GL extensions.
- enumext.spec has a few more synonyms for enums (since it's the
  file used for generating the official glext.h for desktop).

This change only introduces new #define lines to generated-dispatch.h.

v2: Make the statement about "only introduces new #define lines"
    actually true by continuing to emit based on the categories we
    collected during parsing, except with them defined to '1' instead
    of '', to match actual glext definitions and what gets
    autogenerated from enum.ext.

Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
core.py: Fix sporadic loss of tests in summary

The checking in TestrunResult to determine if a file was proper json or
not is very fragile: it assumes that the last line of the file will be
}. Sometimes this triggers and rebuilds a valid json file, dropping the
last test and resulting in python overhead.

This patch replaces that check with a try/except block. This block
attempts to load the json file with json.load, and on failure attempts
to fix the json.

V2: - replaces json.loads with json.load: this was causing an error but
	  being caught by the except block.
	- Corrects issue created by the try block changing file.tell() so
	  that file.seek would fail in self.__repairFile()
V3: - refactor to remove duplicate code

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
oes_fixed_point: Add ES1 test for fixed-point attribute arrays (v2)

Test GL_FIXED with glColorPointer and glVertexPointer. Verifies Mesa
commit 7a9f4d3e.

v2: Remove glViewport and piglit_ortho_projection.

Reviewed-by: Eric Anholt <eric@anholt.net>
Signed-off-by: Chad Versace <chad.versace@linux.intel.com>
glean: Don't link X11 on MacOSX.
glean: Disable on MacOSX.

Simply impossible to get it working these days.
Set config.requires_displayed_window in tests that use front buffers.

When running tests with a non-composited window manager, it isn't safe
to access the front buffer until after the window is shown.  This
patch sets config.requires_displayed_window in tests that access front
buffers, to make sure that the piglit framework exposes the window,
even when testing in "-auto" mode.

Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
util/x11: Wait for expose event in manual mode or with front buffer tests.

When running piglit in manual mode (no "-auto" command-line option is
given), there's no point in calling piglit_display() before the window
is exposed.  This just leads to confusion because it will be called
again once the window appears, leading to duplicate test output in the
console window.

When running piglit in "-auto" mode, if the test accesses the front
buffer, then we need to wait until the window is exposed before
calling piglit_display(), since a front buffer is not guaranteed to be
available before then (in practice, this only happens with
non-compositing window managers).  However, if the test doesn't access
the front buffer, then it is still safe to call piglit_display()
before the expose event; doing so avoids wasting time.

Note: there are two known bugs that cause sporadic failures in certain
piglit tests with Mesa/Intel hardware (and possibly other Mesa
drivers).  See bugs #1 and #2 in
http://lists.freedesktop.org/archives/mesa-dev/2013-May/039985.html.
This change seems to exacerbate those sporadic failures.  As far
as I'm aware, the tests that are affected are:

- spec/!OpenGL 1.1/drawbuffer-modes
- spec/EXT_framebuffer_blit/fbo-sys-blit
- spec/EXT_framebuffer_blit/fbo-sys-sub-blit

I have patches on the list to fix bug #1 from that email (see
http://lists.freedesktop.org/archives/mesa-dev/2013-May/040010.html),
and Eric Anholt is working on bug #2.  I believe that once those fixes
land, the above tests should pass consistently.

Based on work by Chad Versace.

Cc: Chad Versace <chad.versace@linux.intel.com>
Cc: Eric Anholt <eric@anholt.net>

Reviewed-by: Chad Versace <chad.versace@linux.intel.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
Add a parser test for "#version 110 es".

This should fail as there aren't profiles in GLSL 1.10.  It currently
causes assertion failures in Mesa.

Reviewed-by: Matt Turner <mattst88@gmail.com>
Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
Add new tests for GLSL 1.50 #version directives.

GLSL 1.50 introduces the ability to specify profiles on the #version
line.  These new tests ensure #version 150 core is accepted while
invalid profiles are not.  Another new test ensures that the new
GL_core_profile #define is present.  Finally, another test makes sure
__VERSION__ works as expected.

Reviewed-by: Matt Turner <mattst88@gmail.com>
Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
Always print what is being probed

Reviewed-by: Paul Berry <stereotype441@gmail.com>
read-front: modify the test to reproduce an MSAA front buffer bug in st/dri

v2: move the clearing code to piglit_display
Add -samples=n command-line argument forcing MSAA visuals

v2: combining -fbo and -samples should report FAIL

Reviewed-by: Paul Berry <stereotype441@gmail.com>
glx-copy-sub-buffer: accept -samples=n

Reviewed-by: Paul Berry <stereotype441@gmail.com>
all.tests: enable testing of MSAA visuals for a few selected tests

These tests have proved to be useful for implementing and fixing MSAA
visuals.

I also recommend the mesa/demos tests "reflect" and "copypixrate" to test front
buffer MSAA rendering.

Reviewed-by: Paul Berry <stereotype441@gmail.com>
glslparsertest: Fix handling of GL_GEOMETRY_VERTICES_OUT_ARB.

When testing geometry shaders, glslparsertest must set
GL_GEOMETRY_VERTICES_OUT_ARB before linking, since the default value
of this setting (0) is fairly useless.

Previously, we were accidentally passing the shader name to
glProgramParameteri() instead of the program name, causing spurious
errors.

Reviewed-by: Eric Anholt <eric@anholt.net>
cl: Add a test for the phatk kernel used for bitcoin mining
arb_shading_language_420pack: Add line continuation test.
arb_shading_language_420pack: Add UTF-8 test.