- Original Message -
On Wed, Feb 6, 2013 at 4:30 PM, Kristian Høgsberg k...@bitplanet.net
wrote:
On Tue, Feb 5, 2013 at 8:43 AM, jfons...@vmware.com wrote:
From: José Fonseca jfons...@vmware.com
I'd like to test Mesa OpenGL ES along side with NVIDIA libGL
drivers. But
Hi,
If I want to implement some OpesnGL function , say glLoadIdentity.
When I see the function declaration in Mesa or OpenGL its usually defined as :
WINGDIAPI void APIENTRY glLoadIdentity (void);
extern PFNGLLOADIDENTITYPROC __gleLoadIdentity;
#define glLoadIdentity __gleLoadIdentity
And on
_mesa_base_tex_format doesn't accept GL_BGR and GL_ABGR_EXT, etc.
v2: add a (now hopefully complete) helper function to deal with this
NOTE: This is a candidate for the stable branches.
---
src/mesa/main/texgetimage.c | 33 -
1 file changed, 32 insertions(+), 1
On 02/06/2013 11:34 PM, Vinson Lee wrote:
Fixes resource leak defect reported by Coverity.
Signed-off-by: Vinson Leev...@freedesktop.org
---
src/gallium/drivers/nv30/nv30_screen.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/gallium/drivers/nv30/nv30_screen.c
https://bugs.freedesktop.org/show_bug.cgi?id=60395
--- Comment #3 from Brian Paul bri...@vmware.com ---
I see no history of any Mesa patches from you. You should begin by posting
patches for review on the mesa-dev list.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=59238
--- Comment #6 from Maarten Lankhorst m.b.lankho...@gmail.com ---
http://paste.ubuntu.com/1620151/plain/ is the patch I used to reduce visibility
in debian-experimental, I could commit this if there is interest
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=60395
--- Comment #4 from commanderan...@yahoo.com ---
Oh ok. I can get started with the standard patch review process on the mailing
list. Works for me. Thanks gents!
--
You are receiving this mail because:
You are the assignee for the bug.
On Thu, Feb 7, 2013 at 7:06 AM, Marek Olšák mar...@gmail.com wrote:
_mesa_base_tex_format doesn't accept GL_BGR and GL_ABGR_EXT, etc.
v2: add a (now hopefully complete) helper function to deal with this
NOTE: This is a candidate for the stable branches.
---
src/mesa/main/texgetimage.c |
On 02/07/2013 01:57 AM, ritvik_sha...@dell.com wrote:
Hi,
If I want to implement some OpesnGL function , say glLoadIdentity.
When I see the function declaration in Mesa or OpenGL its usually
defined as :
WINGDIAPI void APIENTRY glLoadIdentity (void);
extern PFNGLLOADIDENTITYPROC
On 02/07/2013 05:22 AM, Carlos Olmedo Escobar wrote:
Hi.
As i see in the latest mesa release you are not using gcc
micro-optimizations as hot or cold attributes [1] but you are using
__builtin_expect though. Probably a naive question but have you
considered using them?
https://bugs.freedesktop.org/show_bug.cgi?id=59238
--- Comment #7 from Matt Turner matts...@gmail.com ---
(In reply to comment #6)
http://paste.ubuntu.com/1620151/plain/ is the patch I used to reduce
visibility in debian-experimental, I could commit this if there is interest
Maybe pastebin
On 02/06/2013 03:10 PM, Paul Berry wrote:
Background:
All of the GLSL specs from GLSL 1.30 (and GLSL ES 3.00) onward contain
language requiring certain integer variables to be declared with the
flat keyword, but they differ in exactly *when* the rule is enforced:
(a) GLSL 1.30 and 1.40 say
On Thu, Feb 7, 2013 at 3:37 AM, Jose Fonseca jfons...@vmware.com wrote:
- Original Message -
On Wed, Feb 6, 2013 at 4:30 PM, Kristian Høgsberg k...@bitplanet.net
wrote:
On Tue, Feb 5, 2013 at 8:43 AM, jfons...@vmware.com wrote:
From: José Fonseca jfons...@vmware.com
I'd like
On 7 February 2013 08:40, Brian Paul bri...@vmware.com wrote:
On 02/06/2013 03:10 PM, Paul Berry wrote:
Background:
All of the GLSL specs from GLSL 1.30 (and GLSL ES 3.00) onward contain
language requiring certain integer variables to be declared with the
flat keyword, but they differ in
On 5 February 2013 22:59, Vinson Lee v...@freedesktop.org wrote:
Fixes uninitialized pointer field defect reported by Coverity.
Signed-off-by: Vinson Lee v...@freedesktop.org
Reviewed-by: Paul Berry stereotype...@gmail.com
---
src/glsl/link_varyings.cpp | 4 +++-
1 file changed, 3
From: Michel Dänzer michel.daen...@amd.com
The modifiers don't seem to have any effect with V_MOV_B32, supposedly it's
meant to just move bits untouched.
Fixes 46 piglit tests with radeonsi, though unfortunately 11 of those had
just regressed because they started using the clamp modifier.
On 6 February 2013 23:26, Kenneth Graunke kenn...@whitecape.org wrote:
Haswell's Data Cache data port is a single unit, but split into two
SFIDs to allow for more message types without adding more bits in the
message descriptor.
Untyped Atomic Operations are now message 0010 in the second
https://bugs.freedesktop.org/show_bug.cgi?id=59238
--- Comment #8 from Maarten Lankhorst m.b.lankho...@gmail.com ---
Created attachment 74370
-- https://bugs.freedesktop.org/attachment.cgi?id=74370action=edit
visibility patch for xatracker1
--
You are receiving this mail because:
You are the
On 6 February 2013 23:26, Kenneth Graunke kenn...@whitecape.org wrote:
This is basically a copy and paste of gen7_create_constant_surface, but
with the parameters filled in to offer a simpler interface.
It will diverge shortly.
I didn't bother adding it to the vtable for now since shader
Kenneth Graunke kenn...@whitecape.org writes:
Untyped Atomic Operation messages are illegal for non-RAW formats.
I have no idea why it worked before; the documentation claims it
shouldn't be allowed and the simulator enforces it.
Some arithmetic sleight of hand happens in this patch:
On 6 February 2013 23:26, Kenneth Graunke kenn...@whitecape.org wrote:
Untyped Atomic Operation messages are illegal for non-RAW formats.
I have no idea why it worked before; the documentation claims it
shouldn't be allowed and the simulator enforces it.
Some arithmetic sleight of hand
On Thu, Feb 07, 2013 at 06:28:51PM +0100, Michel Dänzer wrote:
From: Michel Dänzer michel.daen...@amd.com
The modifiers don't seem to have any effect with V_MOV_B32, supposedly it's
meant to just move bits untouched.
Fixes 46 piglit tests with radeonsi, though unfortunately 11 of those had
---
lib/Target/R600/AMDGPUISelLowering.cpp | 10 +++---
lib/Target/R600/AMDGPUISelLowering.h | 1 -
lib/Target/R600/AMDILISelLowering.cpp | 3 ++-
lib/Target/R600/AMDILInstrInfo.td | 1 -
lib/Target/R600/AMDILIntrinsics.td | 10 --
lib/Target/R600/R600Instructions.td
For reasons I don't know, WarCraft 3 under Wine is using glGetTexImage during
rendering, which is killing framerate, and it doesn't seem to be a problem with
Wine, so I decided to optimize that function properly. I implemented
st_GetTexImage using a blit, where the target format exactly matches
This is for glGetTexImage and it will be used for samplers only (which some
drivers already implement by reading util_format_description).
---
src/gallium/auxiliary/util/u_format.csv | 12 +++
src/gallium/auxiliary/util/u_format.h | 123 +++
On 02/06/2013 05:29 PM, Eric Anholt wrote:
The hardware just doesn't support it. I suspect this was a regression from
the move to fixed MESA_FORMATs for compressed textures and that previously we
were storing uncompressed for this or something.
Fixes GPU hangs in piglit texwrap
On 02/06/2013 05:29 PM, Eric Anholt wrote:
In 2 of our checks, we were missing BREAK and CONTINUE.
NOTE: Candidate for the stable branches.
---
src/mesa/drivers/dri/i965/brw_fs.cpp | 33 +++-
src/mesa/drivers/dri/i965/brw_fs.h |1 +
On 02/06/2013 05:29 PM, Eric Anholt wrote:
The code was rather broken for non-XYZW on 8-wide, but all of our
callers were using XYZW anyway. For my experiments with using writemask
on texturing, I've been using manual header setup in the compiler
backends, since we want to actually know what
Kenneth Graunke kenn...@whitecape.org writes:
On 02/06/2013 05:29 PM, Eric Anholt wrote:
In 2 of our checks, we were missing BREAK and CONTINUE.
NOTE: Candidate for the stable branches.
---
src/mesa/drivers/dri/i965/brw_fs.cpp | 33
+++-
From: Tom Stellard thomas.stell...@amd.com
Also output a more useful error message.
NOTE: This is a candidate for the Mesa stable branches
---
lib/Target/R600/AMDGPUISelLowering.h |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/lib/Target/R600/AMDGPUISelLowering.h
From: Tom Stellard thomas.stell...@amd.com
NOTE: This is a candidate for the Mesa stable branches
---
lib/Target/R600/R600Instructions.td |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/lib/Target/R600/R600Instructions.td
b/lib/Target/R600/R600Instructions.td
Should have been done in d9948e49 but I missed it because
MAX_VARYING_FLOATS doesn't appear in the ES 3 spec, but is the same
value as MAX_VARYING_COMPONENTS.
NOTE: Candidate for the 9.1 branch
---
src/mesa/main/get_hash_params.py |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
On 02/07/2013 01:13 PM, Marek Olšák wrote:
This is for glGetTexImage and it will be used for samplers only (which some
drivers already implement by reading util_format_description).
---
src/gallium/auxiliary/util/u_format.csv | 12 +++
src/gallium/auxiliary/util/u_format.h | 123
On 02/07/2013 01:13 PM, Marek Olšák wrote:
This commit allows using glGetTexImage during rendering and still
maintain interactive framerates.
This improves performance of WarCraft 3 under Wine. The framerate is improved
from 25 fps to 39 fps in the main menu, and from 0.5 fps to 32 fps in the
On 02/07/2013 12:13 PM, Marek Olšák wrote:
For reasons I don't know, WarCraft 3 under Wine is using glGetTexImage during
rendering, which is killing framerate, and it doesn't seem to be a problem with
Wine, so I decided to optimize that function properly. I implemented
st_GetTexImage using a
On 02/07/2013 04:37 PM, Matt Turner wrote:
Should have been done in d9948e49 but I missed it because
MAX_VARYING_FLOATS doesn't appear in the ES 3 spec, but is the same
value as MAX_VARYING_COMPONENTS.
NOTE: Candidate for the 9.1 branch
Reviewed-by: Ian Romanick ian.d.roman...@intel.com
---
These were, at some point in the past, used to request that Xorg's
compiler.h export a static inline xf86ReadMmio32 instead of a function
pointer. compiler.h only has this option for DEC Alpha.
But Xorg's compiler.h isn't being included by either of these two files
and the radeon driver still
On 02/07/2013 08:40 AM, Brian Paul wrote:
On 02/06/2013 03:10 PM, Paul Berry wrote:
Background:
All of the GLSL specs from GLSL 1.30 (and GLSL ES 3.00) onward contain
language requiring certain integer variables to be declared with the
flat keyword, but they differ in exactly *when* the rule
In the documentation for BindBufferRange, OpenGL specs from 3.0
through 4.1 contain this language:
The error INVALID_VALUE is generated if size is less than or
equal to zero or if offset + size is greater than the value of
BUFFER_SIZE.
This text was dropped from OpenGL 4.2, and it
On 7 February 2013 17:54, Paul Berry stereotype...@gmail.com wrote:
In the documentation for BindBufferRange, OpenGL specs from 3.0
through 4.1 contain this language:
The error INVALID_VALUE is generated if size is less than or
equal to zero or if offset + size is greater than the
From: Roland Scheidegger srol...@vmware.com
This adds support of the additional blending factors to the blend function
itself, and also enables testing of it in lp_test_blend (which passes).
Still need to add the glue code of linking fs shader outputs to blend inputs
in llvmpipe, and probably
From: Roland Scheidegger srol...@vmware.com
link up the fs outputs and blend inputs, and make sure the second blend source
is correctly loaded and converted (which is quite complex).
There's a slight refactoring of the monster generate_unswizzled_blend()
function where it makes sense to factor
From: Roland Scheidegger srol...@vmware.com
There can be other per-thread data than just vis_counter, so pass a struct
around instead (some of our non-public code uses this already and this
difference is a major cause of merge pain).
---
src/gallium/drivers/llvmpipe/lp_jit.c | 19
From: Ian Romanick ian.d.roman...@intel.com
This matches the behavior of the Windows driver, but a bspec reference
should would be nice.
NOTE: This is a candidate for the 9.0 and 9.1 branches.
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
---
src/mesa/drivers/dri/i965/brw_context.c | 1
On 02/07/2013 07:25 PM, Ian Romanick wrote:
From: Ian Romanick ian.d.roman...@intel.com
This matches the behavior of the Windows driver, but a bspec reference
should would be nice.
NOTE: This is a candidate for the 9.0 and 9.1 branches.
Signed-off-by: Ian Romanick ian.d.roman...@intel.com
---
On 01/31/2013 06:02 PM, Brian Paul wrote:
When glCompressedTexImage is called the internalFormat is a specific
format for the incoming image and the the hardware format should be
^^^
the same (since we never do format transcoding). So use the simpler
On 02/01/2013 09:25 AM, Brian Paul wrote:
On 01/31/2013 04:21 PM, Marek Olšák wrote:
EmitCondCodes is always false.
---
src/mesa/state_tracker/st_glsl_to_tgsi.cpp | 24
++--
1 file changed, 2 insertions(+), 22 deletions(-)
diff --git
On 01/31/2013 08:50 AM, Michel Dänzer wrote:
From: Michel Dänzer michel.daen...@amd.com
GLX uses mapi/glapi/libglapi.la, which is only built for OpenGL.
NOTE: This is a candidate for the stable branches.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=59364
Tested-by: Tom Stellard
On 7 February 2013 19:25, Ian Romanick i...@freedesktop.org wrote:
From: Ian Romanick ian.d.roman...@intel.com
This matches the behavior of the Windows driver, but a bspec reference
should would be nice.
I believe this is the bspec reference you're looking for:
From the Ivy Bridge PRM,
Fixes unused pointer value defect reported by Coverity.
Signed-off-by: Vinson Lee v...@freedesktop.org
---
src/mesa/drivers/dri/intel/intel_tex_copy.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/mesa/drivers/dri/intel/intel_tex_copy.c
Fixes uninitialized scalar field defects reported by Coverity.
Signed-off-by: Vinson Lee v...@freedesktop.org
---
src/glsl/glsl_types.cpp | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/glsl/glsl_types.cpp b/src/glsl/glsl_types.cpp
index 4a2c879..3b066d0 100644
---
There is no rt library on Mac OS X.
Signed-off-by: Vinson Lee v...@freedesktop.org
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=58872
---
configure.ac | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/configure.ac b/configure.ac
index
The brw_vec4 vertex shader backend doesn't treat clip planes specially,
so this code is unnecessary. It was used for the brw_vs_emit backend.
Signed-off-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/drivers/dri/i965/gen6_vs_state.c | 9 -
1 file changed, 4 insertions(+), 5
_NEW_POLYGONSTIPPLE covers the polygon stipple /pattern/, but the enable
flag is covered by _NEW_POLYGON.
NOTE: This is a candidate for stable branches.
Signed-off-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/drivers/dri/i965/brw_wm_state.c | 4 +---
1 file changed, 1 insertion(+), 3
This reorders the brw_bits array in brw_state_upload.c to match the
order of the #defines in brw_context.h.
Otherwise, it's really hard to see if any are missing.
Signed-off-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/drivers/dri/i965/brw_state_upload.c | 10 +-
1 file
These are more recent additions, and no one remembered to update the
INTEL_DEBUG=state code.
Signed-off-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/drivers/dri/i965/brw_state_upload.c | 7 +++
1 file changed, 7 insertions(+)
diff --git
These don't need to be re-disabled on every batch if we're using
hardware contexts. (If we're not, this is equivalent.)
Signed-off-by: Kenneth Graunke kenn...@whitecape.org
---
src/mesa/drivers/dri/i965/gen7_disable.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
57 matches
Mail list logo
