On 30.06.2014 20:03, Matt Turner wrote:
> On Mon, Jun 30, 2014 at 10:37 AM, Ian Romanick wrote:
>> In the cases where a return (with a value) is removed, I'm afraid static
>> analysis tools will start to complain. I'll be surprised if Klocwork
>> understands (or trusts) GCC __builtin_unreachable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 20.02.2014 22:41, schrieb Matt Turner:
> --- src/mesa/drivers/dri/i965/brw_fs.h | 14 +++--- 1 file
> changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/src/mesa/drivers/dri/i965/brw_fs.h
> b/src/mesa/drivers/dri/i965/brw_fs.h index b
Am 28.10.2012 20:51, schrieb Kenneth Graunke:
> This makes sense to me. The original reason for splitting out the ANGLE
> vs. EXT bits was that the ANGLE extension only requires decompression,
> while the other two require both compression and decompression. So that
> one could be advertised eve
On 20.10.2012 01:28, Anuj Phogat wrote:
> This series lives on my etc2-v9 branch (https://github.com/aphogat/mesa).
>
> This series enables 8 out of 10 ETC2 texture formats for all Intel
> hardware by simply decoding the ETC2 data into RGBX data at the time
> of glCompressedTexImage2D. These patch
On 06.09.2012 07:35, j.gli...@gmail.com wrote:
> From: Jerome Glisse
>
> To avoid GPU lockup registers must be emited in a specific order
> (no kidding ...). This patch rework atom emission so order in which
> atom are emited in respect to each other is always the same. We
> don't have any inform
This one doesn't make sense to me: For __GNUC__ it uses
implementation-defined non-standard stuff. For other compilers it
divides by zero, which is undefined behaviour. Why not use standard
macros NAN and INFINITY from math.h? The standard (section 7.12 in the
C11 standard, AFAIK the wording is the
Am 10.08.2011 11:46, schrieb Rudolf Polzer:
> Speaking of BPTC - what is its patent situation? From a quick glance at the
> extension spec, it does seem to use S3TC's interpolation method, so it likely
> is not safe from S3's patents. But I may be wrong there, as BPTC is quite
> messy
> and convol
Am 10.08.2011 08:50, schrieb Marek Olšák:
>
> The problem is there is no adoption of S2TC in the industry. The
> current state is that Unigine products don't run without full S3TC.
> Neither does the id Tech 4 engine. Most, if not all, D3D games
> consider S3TC a standard. In order to succeed, S2
Am 10.08.2011 11:34, schrieb Rudolf Polzer:
>
>> The OpenGL ARB cannot incorporate S3TC into a core spec anyway.
>
> But it already is core part of OpenGL 3.0.
No.
Making S3TC part of OpenGL was discussed, but rejected. OpenGL only
requires RGTC (since OpenGL 3.0) and BPTC (since OpenGL 4.2).
Am 09.08.2011 13:10, schrieb Rudolf Polzer:
> As for compression: the compressed format is basically "each 4x4 block is a
> 2-color optimum palette image". Similar schemes have existed way before S3TC
> […]
See Beers et al., "Rendering from compressed textures" in the SIGGRAPH
'96 proceedings for
Am 21.03.2011 11:43, schrieb Denis Steckelmacher:
> […]
> I'm open to any suggestion. I now understand the majority of the Mesa code (I
> read most of it past week), and I also read some parts of the OpenVG state
> tracker (a state tracker not too far from OpenGL, but way simpler, and built
> di
Am 06.01.2011 07:14, schrieb Arthur Huillet:
>
> It hasn't been committed into master yet but I think the patch at
> https://bugs.freedesktop.org/show_bug.cgi?id=32579
> should go into 7.9.1 and 7.10. Failing that, the problem might be present on
> e.g. the current Ubuntu forever.
>
What about
12 matches
Mail list logo