On Mon, Dec 9, 2013 at 6:00 PM, Anuj Phogat wrote:
> OpenGL with ARB_ES2_compatibility extension allows shaders that specify
> #version 100 and the shader is treated as targeting version 100 of the
> GLSL ES.
> state->es_shader flag might change during parsing based on the #version
> directive men
Cc: mesa-sta...@lists.freedesktop.org
---
src/glsl/glcpp/glcpp-parse.y | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/src/glsl/glcpp/glcpp-parse.y b/src/glsl/glcpp/glcpp-parse.y
index 427fdec..995427a 100644
--- a/src/glsl/glcpp/glcpp-parse.y
+++ b/src/glsl/glcpp/glcpp
---
src/glsl/glcpp/glcpp-parse.y | 1 -
src/glsl/glcpp/glcpp.c | 1 -
2 files changed, 2 deletions(-)
diff --git a/src/glsl/glcpp/glcpp-parse.y b/src/glsl/glcpp/glcpp-parse.y
index c774662..427fdec 100644
--- a/src/glsl/glcpp/glcpp-parse.y
+++ b/src/glsl/glcpp/glcpp-parse.y
@@ -30,7 +30,6 @
---
src/glsl/glsl_parser_extras.cpp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/glsl/glsl_parser_extras.cpp b/src/glsl/glsl_parser_extras.cpp
index 21dc3ab..e67988f 100644
--- a/src/glsl/glsl_parser_extras.cpp
+++ b/src/glsl/glsl_parser_extras.cpp
@@ -50,7 +50,7 @@ glsl
From: Anuj Phogat
OpenGL with ARB_ES2_compatibility allows shaders that specify #version
100.
This fixes the Khronos OpenGL test(Texture_Rectangle_Samplers_frag.test)
failure.
Cc: mesa-sta...@lists.freedesktop.org
Reviewed-by: Matt Turner
Signed-off-by: Anuj Phogat
---
src/glsl/glsl_parser_e
Instead of defining preprocessor macros in glcpp_parser_create based on
the GL API, wait until the shader version has been resolved. Doing this
allows us to correctly set (and not set) preprocessor macros for
extensions allowed by the API but not the shader, as in the case of
ARB_ES3_compatibility.
On Fri, Jan 17, 2014 at 11:58 PM, Ilia Mirkin wrote:
> Signed-off-by: Ilia Mirkin
> ---
>
> This seems like a function that should exist in gallium/util, but I didn't
> find it. I guess the mesa/st does these checks far enough away from actual
> resource creation.
>
> src/gallium/state_trackers/
NV3x cards don't support NPOT textures. Technically this restriction
could be worked around, but since it also doesn't expose any video
decoding hw, just turn it off entirely.
Signed-off-by: Ilia Mirkin
Cc: 10.0
---
src/gallium/state_trackers/vdpau/device.c | 5 +
1 file changed, 5 insertio
Signed-off-by: Ilia Mirkin
---
I can't say I'm happy about re-grabbing the mutex in the error path, but I
assume it must be taken to delete a sampler view. I could move the AddDataHTAB
thing inside the mutex, but I assumed it was like that for a reason -- could
be a perf issue? Or could be a non-
This was prompted by a bug mentioning some fairly impossible errors coming
from plugin-container running flash on a NV34 card. I identified two issues --
the major one is that NV3x cards don't support NPOT textures, so pretty much
everything vdpau does won't work as is. NV4x cards do support NPOT t
Signed-off-by: Ilia Mirkin
---
This seems like a function that should exist in gallium/util, but I didn't
find it. I guess the mesa/st does these checks far enough away from actual
resource creation.
src/gallium/state_trackers/vdpau/bitmap.c| 4
src/gallium/state_trackers/vdpau/out
> >
> > diff --git a/src/glsl/glsl_parser_extras.cpp
> > b/src/glsl/glsl_parser_extras.cpp
> > index 21dc3ab..92076b5 100644
> > --- a/src/glsl/glsl_parser_extras.cpp
> > +++ b/src/glsl/glsl_parser_extras.cpp
> > @@ -484,6 +484,7 @@ struct _mesa_glsl_extension {
> > static const _mesa_glsl_exten
https://bugs.freedesktop.org/show_bug.cgi?id=73757
Priority: medium
Bug ID: 73757
Assignee: mesa-dev@lists.freedesktop.org
Summary: [swrast] SIGSEGV swrast/s_renderbuffer.c:559
Severity: normal
Classification: Unclassified
OS
https://bugs.freedesktop.org/show_bug.cgi?id=73755
Priority: medium
Bug ID: 73755
Keywords: regression
CC: bri...@vmware.com, mar...@gmail.com
Assignee: mesa-dev@lists.freedesktop.org
Summary: [softpipe] piglit fbo-missing-attach
On Fri, Jan 17, 2014 at 5:21 PM, Kristian Høgsberg wrote:
> We call intel_prepare_render() in intelMakeCurrent() to make sure we have
> renderbuffers before calling _mesa_make_current(). The only reason we
> do this is so that we can have valid defaults for width and height.
> If we already have
On 01/17/2014 05:03 PM, Ian Romanick wrote:
> From: Ian Romanick
>
> noop_scissor (correctly) only examines the scissor rectangle for
> viewport 0. Therefore, it should only be called when that scissor
> rectangle is enabled.
>
> Signed-off-by: Ian Romanick
> ---
> src/mesa/drivers/dri/i965/b
We call intel_prepare_render() in intelMakeCurrent() to make sure we have
renderbuffers before calling _mesa_make_current(). The only reason we
do this is so that we can have valid defaults for width and height.
If we already have buffers for the drawable we're making current, we
don't need to do
From: Ian Romanick
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/main/attrib.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/src/mesa/main/attrib.c b/src/mesa/main/attrib.c
index db659ad..7b7cf0e 100644
--- a/src/mesa/main/attrib.c
+++ b/s
From: Courtney Goeltzenleuchter
v2 (idr): Only enable the extension on GEN7+ w/core profile because it
requires geometry shaders.
v3 (idr): Add some casting to fix setting of ViewportBounds.Min.
Negating an unsigned value, then casting to float doesn't do what you
might think it does.
Signed-of
From: Ian Romanick
noop_scissor (correctly) only examines the scissor rectangle for
viewport 0. Therefore, it should only be called when that scissor
rectangle is enabled.
Signed-off-by: Ian Romanick
---
src/mesa/drivers/dri/i965/brw_clear.c | 2 +-
src/mesa/drivers/dri/radeon/radeon_co
From: Ian Romanick
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/main/attrib.c | 2 +-
src/mesa/main/context.c | 2 +-
src/mesa/main/scissor.c | 6 +++---
src/mesa/main/scissor.h | 2 +-
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/src/mesa/main/attri
From: Ian Romanick
This variable is handled in a fashion identical to gl_Layer.
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/brw_vec4_visitor.cpp | 4
src/mesa/drivers/dri/i965/brw_vs.c | 6 +++---
2 files changed, 7 insertions(+), 3
From: Ian Romanick
Create an internal function that just writes data into the depth range.
In future patches this will see more use because we only want to call
dd_function_table::DepthRange once after setting all of the depth ranges
instead of once per depth range.
Signed-off-by: Ian Romanick
From: Ian Romanick
Drivers that currently use _Xmin and friends to set their scissor
rectangle will need to use this code directly once they are updated for
GL_ARB_viewport_array.
v2: Use different bit-test idiom and fix mixed tabs and spaces. Both
were suggested by Ken.
Signed-off-by: Ian Rom
From: Ian Romanick
In _mesa_Scissor, make sure that ctx->Driver.Scissor is only called once
instead of once per scissor rectangle.
v2: Use MAX_VIEWPORTS instead of ctx->Const.MaxViewports because the
driver may not set ctx->Const.MaxViewports yet.
Signed-off-by: Ian Romanick
Reviewed-by: Kenne
From: Ian Romanick
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/gen6_clip_state.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/gen6_clip_state.c
b/src/mesa/drivers/dri/i965/gen6_clip_stat
From: Ian Romanick
This matches the expectations of GL_ARB_viewport_array and the storage
type where the values will land.
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/main/viewport.c | 13 +++--
src/mesa/main/viewport.h | 4 ++--
2 files changed, 9 insertion
From: Ian Romanick
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/glsl/glcpp/glcpp-parse.y| 3 +++
src/glsl/glsl_parser_extras.cpp | 1 +
src/glsl/glsl_parser_extras.h | 2 ++
src/glsl/standalone_scaffolding.cpp | 1 +
4 files changed, 7 insertions(+)
diff
From: Ian Romanick
At least for GEN7+, anyway.
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
docs/GL3.txt| 2 +-
docs/relnotes/10.1.html | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/docs/GL3.txt b/docs/GL3.txt
index 0672ec7..3bded7d 100644
--
From: Courtney Goeltzenleuchter
v2 (idr): Use set_viewport_no_notify / set_depth_range_no_notify (and
manually notify the driver) instead of calling _mesa_set_viewporti /
_mesa_set_depthrangei. Refactor bodies of _mesa_ViewportIndexed and
_mesa_ViewportIndexedv into a shared function. Remove sp
From: Ian Romanick
v2: Use MAX_VIEWPORTS instead of ctx->Const.MaxViewports because the
driver may not set ctx->Const.MaxViewports yet.
v3: Handle all viewport entries in update_viewport_matrix and
_mesa_copy_context too. This was previously in an earlier patch.
Having the code in the earlier p
From: Ian Romanick
Currently MaxViewports is still 1, so this won't affect any change.
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/brw_cc.c | 21 +
src/mesa/drivers/dri/i965/brw_defines.h | 1 +
src/mesa/drivers/dri/i965
From: Courtney Goeltzenleuchter
v2 (idr): Fix copy-and-paste bug... s/LAYER/VIEWPORT/
Signed-off-by: Courtney Goeltzenleuchter
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/glsl/builtin_variables.cpp | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/glsl/builtin_va
From: Ian Romanick
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/main/mtypes.h| 2 ++
src/mesa/program/prog_print.c | 10 ++
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/src/mesa/main/mtypes.h b/src/mesa/main/mtypes.h
index cac0206..25
From: Ian Romanick
These limits will be queryable by GL_MAX_VIEWPORTS,
GL_VIEWPORT_SUBPIXEL_BITS, and GL_VIEWPORT_BOUNDS_RANGE. Drivers that
actually implement the extension must set values for these constants
that comply with the minimum-maximums from the spec.
Most of these changes were part
From: Courtney Goeltzenleuchter
Define API connections to extension entry points added in previous
commits. Update entry points to use floating point arguments as
required by the extension.
Add get tokens for ARB_viewport_array state.
v2: Include review feedback.
v3 (idr): Fix 'make check'. Ad
From: Ian Romanick
Create an internal function that just writes data into the viewport. In
future patches this will see more use because we only want to call
dd_function_table::Viewport once after setting all of the viewport
instead of once per viewport.
Signed-off-by: Ian Romanick
Reviewed-by
From: Ian Romanick
In _mesa_Viewport and _mesa_DepthRange, make sure that
ctx->Driver.Viewport is only called once instead of once per viewport or
depth range.
v2: Make _mesa_DepthRange actually set all of the depth ranges (instead
of just index 0). Noticed by Ken.
Signed-off-by: Ian Romanick
From: Courtney Goeltzenleuchter
Only element 0 of the array is used anywhere at this time, so there
should be no changes.
v4: Split out from a single megapatch. Suggested by Ken.
Signed-off-by: Courtney Goeltzenleuchter
Signed-off-by: Ian Romanick
---
src/mesa/drivers/common/meta.c
From: Ian Romanick
Internal callers should do the right thing.
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/main/viewport.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/src/mesa/main/viewport.c b/src/mesa/main/viewport.c
ind
From: Ian Romanick
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/drivers/common/meta.c | 14 +++---
src/mesa/main/context.c| 2 +-
src/mesa/main/viewport.c | 24 ++--
src/mesa/main/viewport.h | 2 +-
4 files changed, 23
From: Courtney Goeltzenleuchter
v2 (idr): Fix several "comparison between signed and unsigned integer
expressions" warnings.
Signed-off-by: Courtney Goeltzenleuchter
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/main/get.c | 189 +++
From: Ian Romanick
Create an internal function that just writes data into the scissor
rectangle. In future patches this will see more use because we only
want to call dd_function_table::Scissor once after setting all of the
scissor rectangles instead of once per scissor rectangle.
Signed-off-by
From: Ian Romanick
Previously the restore code would enable all scissor rectangles if any
scissor rectangles were enabled on entry to meta. When there is only
one scissor rectangle, this is fine. As soon as a driver supports
multiple viewports, this will be a problem.
Signed-off-by: Ian Romani
From: Courtney Goeltzenleuchter
v4: Split out from a single megapatch. Suggested by Ken. Also make
meta's save_state::ViewportX, ::ViewportY, ::ViewportW, and ::ViewportH
to match gl_viewport_attrib.
Signed-off-by: Courtney Goeltzenleuchter
Signed-off-by: Ian Romanick
---
src/mesa/drivers/c
From: Ian Romanick
Currently MaxViewports is still 1, so this won't affect any change.
v2: Minor code reformatting suggested by Ken.
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/drivers/dri/i965/gen6_scissor_state.c | 60 ++
1 file changed, 33
From: Courtney Goeltzenleuchter
Now that the scissor enable state is a bitfield need a custom function
to extract the correct value from gl_context. Modeled
Scissor.EnableFlags after Color.BlendEnabled.
Signed-off-by: Courtney Goeltzenleuchter
Reviewed-by: Kenneth Graunke
---
src/mesa/main/e
From: Ian Romanick
At various stages the hardware clamps the gl_ViewportIndex to these
values. Setting them to zero effectively makes gl_ViewportIndex be
ignored. This is acutally useful in blorp (so that we don't have to
modify all of the viewport / scissor state).
v2: Use INTEL_MASK to creat
From: Courtney Goeltzenleuchter
v2 (idr): Use set_scissor_no_notify (and manually notify the driver)
instead of calling _mesa_set_scissori. Refactory bodies of
_mesa_ScissorIndexed and _mesa_ScissorIndexedv into a shared function.
Perform parameter validation in the same order in all three funct
From: Courtney Goeltzenleuchter
v4: Split out from a single megapatch. Suggested by Ken.
Signed-off-by: Ian Romanick
---
src/mesa/main/get.c | 5 +
src/mesa/main/get_hash_params.py | 2 +-
src/mesa/main/mtypes.h | 2 +-
src/mesa/main/viewport.c | 4 ++--
src
From: Ian Romanick
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/mesa/main/attrib.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/src/mesa/main/attrib.c b/src/mesa/main/attrib.c
index f55433e..db659ad 100644
--- a/src/mesa/main/attrib.
From: Courtney Goeltzenleuchter
This will be used when the viewport near and far plane are stored as
doubles instead of as floats.
v4 (idr): Split out from a single megapatch. Suggested by Ken. Also
drop value_double_4. It's never used anywhere in the patch series.
Signed-off-by: Courtney Go
From: Courtney Goeltzenleuchter
Update Mesa and drivers to access updated gl_scissor_attrib.
Now have an enable bitfield and array of gl_scissor_rects.
Drivers have been updated to the new scissor enable state
attribute (gl_context.scissor.EnableFlags) but still treat it
as a single boolean which
From: Courtney Goeltzenleuchter
v2 (idr): Split these changes out from the original patch. Only
advertise GL_ARB_viewport_array in a core profile because it requires
geometry shaders.
Signed-off-by: Courtney Goeltzenleuchter
Signed-off-by: Ian Romanick
Reviewed-by: Kenneth Graunke
---
src/m
This is the overall v2 of the GL_ARB_viewport_array series. It is
mostly the same as the previous series, but there are some differences
worth noting.
Patch "i965: Consider all scissor rectangles in noop_scissor" in the
original series was replaced by "i965: Consider only the scissor
rectangle fo
On Sat, Jan 18, 2014 at 12:45 AM, Mark Mueller wrote:
>
>
>
> On Fri, Jan 17, 2014 at 1:24 PM, Marek Olšák wrote:
>>
>> Incorrect. You have to manually check if the pack and unpack functions
>> access the components using bitwise operations or arrays.
>>
>> Consider char pix[]. The array formats
On Fri, Jan 17, 2014 at 1:24 PM, Marek Olšák wrote:
> Incorrect. You have to manually check if the pack and unpack functions
> access the components using bitwise operations or arrays.
>
> Consider char pix[]. The array formats use arrays for accessing, for
> example:
>
> char *p = &pix[(y*width+
https://bugs.freedesktop.org/show_bug.cgi?id=73100
Michał Górny changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Previously, time spent in geometry shaders would be counted as part of
the vertex shader time.
---
src/mesa/drivers/dri/i965/brw_context.h | 3 +++
src/mesa/drivers/dri/i965/brw_program.c | 10 +-
src/mesa/drivers/dri/i965/brw_vec4.cpp
On 01/17/2014 02:14 PM, Paul Berry wrote:
> These messages are in code that is shared between the VS and GS
> back-ends, so use the terminology "vec4" to avoid confusion.
Reviewed-by: Ian Romanick
> ---
> src/mesa/drivers/dri/i965/brw_vec4_generator.cpp | 8
> src/mesa/drivers/dri/i965
Reviewed-by: Matt Turner
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
From: Tom Stellard
This enables piglit to run and interpret the results from OpenCV's
gtest based opencv_test_ocl program.
This patch adds two new CMake configuration variables:
OPENCL_OpenCVTestOCL_BINDIR: You can use this variable to enable
the OpenCV tests by setting it to the full path of t
https://bugs.freedesktop.org/show_bug.cgi?id=73631
--- Comment #2 from Emil Velikov ---
Nice one Ian, adding "precision mediump float;" before the vec4 variable
declaration in the fragment shader did the job.
Running nouveau on a nv96, in case it matters.
--
You are receiving this mail because
These messages are in code that is shared between the VS and GS
back-ends, so use the terminology "vec4" to avoid confusion.
---
src/mesa/drivers/dri/i965/brw_vec4_generator.cpp | 8
src/mesa/drivers/dri/i965/brw_vec4_visitor.cpp | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
https://bugs.freedesktop.org/show_bug.cgi?id=73631
--- Comment #1 from Ian Romanick ---
It sounds like the shader is broken. Probably just add
precision mediump float;
at global scope before any float (or vec, or mat) types are used.
--
You are receiving this mail because:
You are the assign
- Original Message -
> On 01/17/2014 12:56 PM, Ian Romanick wrote:
> > On 01/17/2014 08:33 AM, jfons...@vmware.com wrote:
> >> diff --git a/src/mesa/drivers/dri/r200/r200_context.c
> >> b/src/mesa/drivers/dri/r200/r200_context.c
> >> index f82424b..f613e56 100644
> >> --- a/src/mesa/drive
On Thu, Dec 19, 2013 at 1:40 PM, Matt Turner wrote:
> Transforms, for example,
>
> mul vgrf3, vgrf2, vgrf1
> mov.sat vgrf4, vgrf3
>
> into
>
> mul.sat vgrf3, vgrf2, vgrf1
> mov vgrf4, vgrf3
>
> which gives register_coalescing an opportunity to remove the MOV
> instruction.
>
> total instru
Ken,
Assuming the caches don't completely derail things, you ought to be
able to make this work with pretty minimal impact:
- Keep the low four bits of the sampler index where they are
- If the 5th bit is set:
- Force message header on
- Add 16*sizeof(sampler_state) to the copy of r0.3 in
On 01/17/2014 12:41 PM, Mark Mueller wrote:
On Fri, Jan 17, 2014 at 8:58 AM, Brian Paul mailto:bri...@vmware.com>> wrote:
On 01/17/2014 03:45 AM, Mark Mueller wrote:
Change all 4 color component unsigned byte formats to meet spec:
s/MESA_FORMAT_RGBA\b/MESA___FORMAT
Incorrect. You have to manually check if the pack and unpack functions
access the components using bitwise operations or arrays.
Consider char pix[]. The array formats use arrays for accessing, for example:
char *p = &pix[(y*width+x)*4];
p[0] = r;
p[1] = g;
p[2] = b;
p[3] = a;
Packed formats use
On 01/17/2014 01:08 PM, Marek Olšák wrote:
> The test seems to work correctly with 32 textures per stage. It tests
> that all textures return the correct color, but the sampler state is
> always the same.
Which is the problem. The method we're using to access samplers works
fine for up to 16, but
With Kristian's comment about keeping the original copyright notices
intact addressed, patches 1, 2, 3, 4, 7, 8, and 10 are
Reviewed-by: Ian Romanick
On 12/14/2013 11:28 AM, Rob Clark wrote:
> From: Rob Clark
>
> It seems that over time, code related to finding driver name, dealing
> with pci-
On Thu, Dec 19, 2013 at 1:40 PM, Matt Turner wrote:
Could you add some commit message text?
Maybe with a small example.
> total instructions in shared programs: 1520829 -> 1511991 (-0.58%)
> instructions in affected programs: 559725 -> 550887 (-1.58%)
> GAINED:
The test seems to work correctly with 32 textures per stage. It tests
that all textures return the correct color, but the sampler state is
always the same.
Marek
On Thu, Jan 16, 2014 at 1:28 AM, Kenneth Graunke wrote:
> On 01/15/2014 12:56 PM, Chris Forbes wrote:
>> Does this actually work for >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/16/2014 10:42 PM, scarp wrote:
> Hi,
>
> I originally posted this to dri-users and got no response. I
> thought about it further and decided it's really a bug and deserves
> to be posted to dri-devel, after all it is a crash and crashes are
> su
On 01/17/2014 12:56 PM, Ian Romanick wrote:
On 01/17/2014 08:33 AM, jfons...@vmware.com wrote:
diff --git a/src/mesa/drivers/dri/r200/r200_context.c
b/src/mesa/drivers/dri/r200/r200_context.c
index f82424b..f613e56 100644
--- a/src/mesa/drivers/dri/r200/r200_context.c
+++ b/src/mesa/drivers/dri
On 01/17/2014 08:33 AM, jfons...@vmware.com wrote:
> diff --git a/src/mesa/drivers/dri/r200/r200_context.c
> b/src/mesa/drivers/dri/r200/r200_context.c
> index f82424b..f613e56 100644
> --- a/src/mesa/drivers/dri/r200/r200_context.c
> +++ b/src/mesa/drivers/dri/r200/r200_context.c
> @@ -29,7 +29,7
This will be useful in my next patch which depends on a functionality
of _mesa_get_min_invocations_per_fragment() to ignore the sample
qualifier (prog->IsSample) based on a flag passed to it.
Signed-off-by: Anuj Phogat
Cc: Chris Forbes
Cc: mesa-sta...@lists.freedesktop.org
---
src/mesa/drivers/
Current implementation of arb_sample_shading doesn't set 'Barycentric
Interpolation Mode' correctly. We use pixel barycentric coordinates
for per sample shading. Instead we should select perspective sample
or non-perspective sample barycentric coordinates.
It also enables using sample barycentric
This patch handles the use of 'centroid' qualifier with 'in' variables
in a fragment shader when persample shading is enabled. Per sample
shading for the whole fragment shader can be enabled by:
glEnable(GL_SAMPLE_SHADING) or using {gl_SamplePosition, gl_SampleID}
builtin variables in fragment shad
Brian Paul writes:
> On 01/17/2014 08:33 AM, jfons...@vmware.com wrote:
>> From: José Fonseca
>>
>> I was the sole author, as Tungsten Graphics employee, which was since
>> then acquired by VMware Inc.
>> ---
>> src/gallium/drivers/trace/trace.xsl | 36
>> ++--
On Fri, Jan 17, 2014 at 8:58 AM, Brian Paul wrote:
> On 01/17/2014 03:45 AM, Mark Mueller wrote:
>
>> Change all 4 color component unsigned byte formats to meet spec:
>> s/MESA_FORMAT_RGBA\b/MESA_FORMAT_ABGR_UNORM8/g
>> s/MESA_FORMAT_RGBA_REV\b/MESA_FORMAT_RGBA_UNORM8/g
>> s/MESA_FO
On 01/13/2014 10:28 PM, Eric Anholt wrote:
> The original intent was that we'd keep a driver-private copy, and there
> would be the normal copy for swrast to make use of without the tuning (or
> anything more invasive we might do) specific to i965. Only, we don't
> generate swrast code any more, b
On Thu, Dec 19, 2013 at 1:40 PM, Matt Turner wrote:
> total instructions in shared programs: 1520829 -> 1511991 (-0.58%)
> instructions in affected programs: 559725 -> 550887 (-1.58%)
> GAINED:6
> LOST: 9
> ---
> src/mesa/driver
https://bugs.freedesktop.org/show_bug.cgi?id=73746
--- Comment #2 from Thomas Rohloff ---
(In reply to comment #1)
> Did you compile Mesa with --enable-gallium-egl?
Yes. Also with other games (for example: Left 4 Dead 2) it works.
--
You are receiving this mail because:
You are the assignee fo
From: Roland Scheidegger
Instead of skipping x/y clipping completely if there's point_tri_clip points
use guard band clipping. This should be easier (previously we could not disable
generating the x/y bits in the clip mask for llvm path, hence requiring custom
clip path), and it also allows us to
https://bugs.freedesktop.org/show_bug.cgi?id=73746
--- Comment #1 from Marek Olšák ---
Did you compile Mesa with --enable-gallium-egl?
--
You are receiving this mail because:
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.f
On 14 January 2014 03:35, Tapani Pälli wrote:
> On 01/14/2014 01:24 AM, Paul Berry wrote:
>
> On 2 January 2014 03:58, Tapani Pälli wrote:
>
> + var->state_slots = NULL;
>> +
>> + if (var->num_state_slots > 0) {
>> + var->state_slots = ralloc_array(var, ir_state_slot,
>> + va
On 14 January 2014 02:35, Tapani Pälli wrote:
> On 01/13/2014 08:27 PM, Paul Berry wrote:
>
> On 2 January 2014 03:58, Tapani Pälli wrote:
>
>> Class will be used by the shader binary cache implementation.
>>
>> Signed-off-by: Tapani Pälli
>> ---
>> src/glsl/memory_writer.h | 147
>> +
On 01/17/2014 03:45 AM, Mark Mueller wrote:
Change all 4 color component unsigned byte formats to meet spec:
s/MESA_FORMAT_RGBA\b/MESA_FORMAT_ABGR_UNORM8/g
s/MESA_FORMAT_RGBA_REV\b/MESA_FORMAT_RGBA_UNORM8/g
s/MESA_FORMAT_ARGB\b/MESA_FORMAT_BGRA_UNORM8/g
s/MESA_FORMAT_ARGB_
On 15 January 2014 02:46, Tapani wrote:
> On 01/14/2014 07:53 PM, Paul Berry wrote:
>
> On 2 January 2014 03:58, Tapani Pälli wrote:
>
>> +static void
>>> +serialize_uniform_storage(gl_uniform_storage *uni, memory_writer &blob)
>>>
>>
>> I don't think this is right. The ARB_get_program_bina
On 01/16/2014 10:13 PM, Mark Mueller wrote:
This series encompases the much discussed specification and renaming of
MESA_FORMATs,
which now is packed into 8 patches
Signed-off-by: Mark Mueller
---
Well, our other enum typedefs (and structs) all use the gl_ prefix. But
the other enum values
On 16 January 2014 05:37, Tapani Pälli wrote:
> On 01/15/2014 06:13 PM, Paul Berry wrote:
>
> On 2 January 2014 03:58, Tapani Pälli wrote:
>
>> Signed-off-by: Tapani Pälli
>> ---
>> src/mesa/main/shaderapi.c | 44
>> ++--
>> 1 file changed, 38 insertion
https://bugs.freedesktop.org/show_bug.cgi?id=73746
Priority: medium
Bug ID: 73746
Assignee: mesa-dev@lists.freedesktop.org
Summary: Gallum HUD not always visible with Rust
Severity: normal
Classification: Unclassified
OS: All
On 01/17/2014 08:33 AM, jfons...@vmware.com wrote:
From: José Fonseca
I was the sole author, as Tungsten Graphics employee, which was since
then acquired by VMware Inc.
---
src/gallium/drivers/trace/trace.xsl | 36 ++--
1 file changed, 22 insertions(+), 14 del
From: José Fonseca
I was the sole author, as Tungsten Graphics employee, which was since
then acquired by VMware Inc.
---
src/gallium/drivers/trace/trace.xsl | 36 ++--
1 file changed, 22 insertions(+), 14 deletions(-)
diff --git a/src/gallium/drivers/trace/trace
On Thu, Jan 16, 2014 at 6:55 PM, Emil Velikov wrote:
> On 16/01/14 23:29, Kristian Høgsberg wrote:
>> On Sat, Jan 11, 2014 at 04:51:42PM -0500, Rob Clark wrote:
>>> On Sat, Jan 11, 2014 at 11:54 AM, Emil Velikov
>>> wrote:
This is an updated series of Rob's patches
* The introduct
On Fri, Jan 10, 2014 at 02:29:04PM -0800, Matt Turner wrote:
> On Wed, Dec 25, 2013 at 2:11 AM, Pohjolainen, Topi
> wrote:
> > On Thu, Dec 19, 2013 at 01:40:23PM -0800, Matt Turner wrote:
> >> Previously we simply considered two registers whose live ranges
> >> overlapped to interfere. Cases such
- Original Message -
> Fixes regression since 9baa45f78b8ca7d66280e36009b6a685055d7cd6
> but some of the piglit fbo-drawbuffers-none tests still don't
> pass.
> ---
> src/gallium/drivers/svga/svga_pipe_clear.c | 10 +++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff -
- Original Message -
> From: Roland Scheidegger
>
> The whole round-pointsize-to-int stuff must only be done with GL legacy
> rules (no point_quad_rasterization) or all the wrong edges are lit up.
> This was previously in a private branch (d3d pointsprite test complains
> loudly otherwise
1 - 100 of 110 matches
Mail list logo
