On Tue, Feb 21, 2017 at 7:45 PM, Timothy Arceri wrote:
> For gpu generations that use LLVM we create a timestamp string
> containing both the LLVM and Mesa build times, otherwise we just
> use the Mesa build time.
Why not use the build id for Mesa?
On Wed, Feb 22, 2017 at 12:06 AM, Iago Toral Quiroga wrote:
> From: Iago Toral Quiroga
Oops :)
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
On Sun, Feb 19, 2017 at 3:23 PM, Eric Engestrom wrote:
> Tested with dEQP-EGL.functional.get_proc_address.*
>
> Signed-off-by: Eric Engestrom
> ---
> src/egl/main/eglapi.c | 37 -
> 1 file changed, 24 insertions(+), 13
On Sat, Feb 18, 2017 at 1:31 PM, Jacob Lifshay wrote:
> This commit improves the message by telling them that they could probably
> enable DRI3. More importantly, it includes a little heuristic to check
> to see if we're running on AMD or NVIDIA's proprietary X11
On Fri, Feb 17, 2017 at 4:59 PM, Eric Engestrom wrote:
> Hey all,
>
> I (finally) set up the git hook, which means that the website [1] is now
> automagically updated whenever a change in docs/* on master is pushed.
>
> There might be bugs, and I'll be doing some other git hook
Nice, thanks.
Reviewed-by: Matt Turner <matts...@gmail.com>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
NG BUT NOT LIMITED TO THE WARRANTIES OF
> MERCHANTABILITY,
> +* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
> SHALL THE
> +* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> +* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
&g
On Fri, Feb 17, 2017 at 1:56 AM, Kenneth Graunke wrote:
> The only feature over and above ES 3.0 is DrawTransformFeedback().
>
> We already have to do the whole SOL_NUM_PRIMS_WRITTEN counter dance in
> order to compute the SVBI value for ResumeTransformFeedback(), at which
On Thu, Feb 16, 2017 at 4:29 AM, Lionel Landwerlin
wrote:
> Intel produces fairly beefy Xeon servers on which it would be nice to be
> able to run shader-db to get some results pretty fast. Unfortunately those
> don't ship with any intel graphics IP (only ancient
an Gray <j...@jsg.id.au> wrote:
>>> > On Wed, Feb 15, 2017 at 11:11:50AM -0800, Matt Turner wrote:
>>> >> Provides the ability to read the .note.gnu.build-id section of ELF
>>> >> binaries, which is inserted by the --build-id=... flag to ld.
>>> >>
On Tue, Feb 14, 2017 at 1:45 PM, Kenneth Graunke wrote:
> diff --git a/src/mesa/drivers/dri/i965/intel_batchbuffer.h
> b/src/mesa/drivers/dri/i965/intel_batchbuffer.h
> index bf7cadfc4d6..da8f7e561f4 100644
> --- a/src/mesa/drivers/dri/i965/intel_batchbuffer.h
> +++
On Thu, Feb 16, 2017 at 9:11 AM, Hugues Evrard wrote:
> Hi all,
>
> I'm a researcher at Imperial College London, my group is working on a
> testing framework for graphics drivers, in particular shader compilers,
> and we would like to get in touch with Mesa shader
ion doesn't say this.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=99660
>
No newline here.
> Signed-off-by: Samuel Iglesias Gonsálvez <sigles...@igalia.com>
> Tested-by: Mark Janes <mark.a.ja...@intel.com>
Reviewed-by: Matt Turner <matts...@gmail.com>
On Thu, Feb 16, 2017 at 4:29 AM, Lionel Landwerlin
wrote:
> Signed-off-by: Lionel Landwerlin
> ---
> run.c | 7 +--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/run.c b/run.c
> index 2654bff..d2ec8c6 100644
Provides the ability to read the .note.gnu.build-id section of ELF
binaries, which is inserted by the --build-id=... flag to ld.
Reviewed-by: Emil Velikov
---
configure.ac | 6 +++
src/util/Makefile.sources | 2 +
src/util/build_id.c | 109
The --build-id=... ld flag has been present since binutils-2.18,
released 28 Aug 2007.
---
src/intel/vulkan/Makefile.am | 1 +
src/intel/vulkan/anv_device.c | 28 +++-
2 files changed, 8 insertions(+), 21 deletions(-)
diff --git a/src/intel/vulkan/Makefile.am
On Wed, Feb 15, 2017 at 6:05 AM, Emil Velikov <emil.l.veli...@gmail.com> wrote:
> Hi Matt,
>
> On 14 February 2017 at 23:58, Matt Turner <matts...@gmail.com> wrote:
>> The --build-id=... ld flag has been present since binutils-2.18,
>> released 28 Aug 2007.
>&g
ot;GNU\0" strcmp is
> applicable and not another string ? Worth adding a note/comment ?
It's generated by GNU ld in all cases I'm aware of, so I think it's the same.
> On 14 February 2017 at 23:58, Matt Turner <matts...@gmail.com> wrote:
>> Provides the ability to read t
Reviewed-by: Matt Turner <matts...@gmail.com>
Please commit ASAP.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Tue, Feb 14, 2017 at 3:52 PM, Jason Ekstrand wrote:
> The new version does a SHA1 sum of the timestamp together with the
> device PCI ID. This fixes a theoretical bug where, if you moved a drive
> between machines, you could end up trying to use a pipeline cache from
>
Provides the ability to read the .note.gnu.build-id section of ELF
binaries, which is inserted by the --build-id=... flag to ld.
---
configure.ac | 2 +
src/util/Makefile.sources | 2 +
src/util/build_id.c | 110 ++
The --build-id=... ld flag has been present since binutils-2.18,
released 28 Aug 2007.
---
src/intel/vulkan/Makefile.am | 1 +
src/intel/vulkan/anv_device.c | 28 +++-
2 files changed, 8 insertions(+), 21 deletions(-)
diff --git a/src/intel/vulkan/Makefile.am
On Tue, Feb 14, 2017 at 12:43 PM, Nicholas Miell <nmi...@gmail.com> wrote:
> On 02/14/2017 12:30 PM, Chad Versace wrote:
>>
>> On Tue 14 Feb 2017, Matt Turner wrote:
>>>
>>> Provides the ability to read the .note.gnu.build-id section of ELF
>>&g
On Tue, Feb 14, 2017 at 11:39 AM, Kristian H. Kristensen
<k...@bitplanet.net> wrote:
> Matt Turner <matts...@gmail.com> writes:
>> diff --git a/src/util/build_id.c b/src/util/build_id.c
>> new file mode 100644
>> index 000..a2e21b7
>> --- /dev/null
On Tue, Feb 14, 2017 at 11:21 AM, Matt Turner <matts...@gmail.com> wrote:
> On Tue, Feb 14, 2017 at 11:18 AM, Matt Turner <matts...@gmail.com> wrote:
>> On Tue, Feb 14, 2017 at 10:59 AM, Jason Ekstrand <ja...@jlekstrand.net>
>> wrote:
>>> I'm not s
On Tue, Feb 14, 2017 at 11:18 AM, Matt Turner <matts...@gmail.com> wrote:
> On Tue, Feb 14, 2017 at 10:59 AM, Jason Ekstrand <ja...@jlekstrand.net> wrote:
>> I'm not sure how I feel about the silent fall-backs. At least in the Vulkan
>> driver, we should fail to compi
On Tue, Feb 14, 2017 at 10:59 AM, Jason Ekstrand wrote:
> I'm not sure how I feel about the silent fall-backs. At least in the Vulkan
> driver, we should fail to compile if we can't get build-id. Otherwise,
> you'll end up compiling a driver that will always fail device
On Tue, Feb 7, 2017 at 3:31 PM, Timothy Arceri <t_arc...@yahoo.com.au> wrote:
> On Tue, 2017-02-07 at 23:58 +0100, Matt Turner wrote:
>> On Tue, Feb 7, 2017 at 4:42 AM, Timothy Arceri <tarc...@itsqueeze.com
>> > wrote:
>> > This series adds support for
The --build-id=... ld flag has been present since binutils-2.18,
released 28 Aug 2007.
---
src/intel/vulkan/Makefile.am | 1 +
src/intel/vulkan/anv_device.c | 31 ---
2 files changed, 13 insertions(+), 19 deletions(-)
diff --git a/src/intel/vulkan/Makefile.am
Provides the ability to read the .note.gnu.build-id section of ELF
binaries, which is inserted by the --build-id=... flag to ld.
---
configure.ac | 2 +
src/util/Makefile.sources | 2 +
src/util/build_id.c | 109 ++
On Tue, Feb 14, 2017 at 7:35 AM, Grazvydas Ignotas wrote:
> On Tue, Feb 14, 2017 at 3:12 PM, Haridasan, Sujith
> wrote:
>> I am using mesa 12.0.1 from yocto project
>>
ors;"
Reviewed-by: Matt Turner <matts...@gmail.com>
I'll give it a day or so before I commit it, so others have an
opportunity to comment.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Mon, Feb 13, 2017 at 3:25 AM, Lonnberg, Toni wrote:
> ---
We need a summary message that gives an overview of what's going on.
I see at least the following changes:
- Colon before the register type
- Semi-colon instead of comma after VertStride
- Printing
On Mon, Feb 13, 2017 at 3:25 AM, Lonnberg, Toni wrote:
> ---
> src/mesa/drivers/dri/i965/brw_disasm.c | 109
> +++--
> src/mesa/drivers/dri/i965/brw_inst.h | 31 +-
> 2 files changed, 135 insertions(+), 5 deletions(-)
>
> diff
Patches' titles should have a prefix. These should likely be "i965: "
Also, I don't know what you mean by a label. The target of an
unstructured jump? The commit message should explain and provide some
background information.
On Mon, Feb 13, 2017 at 3:25 AM, Lonnberg, Toni
On Wed, Feb 8, 2017 at 6:03 PM, Marek Olšák wrote:
> From: Marek Olšák
>
> ---
> src/gallium/include/state_tracker/st_api.h | 19 +++
> src/gallium/state_trackers/dri/dri_context.c| 10 ++
>
On Thu, Feb 9, 2017 at 3:03 PM, Marek Olšák <mar...@gmail.com> wrote:
> On Thu, Feb 9, 2017 at 1:52 PM, Ian Romanick <i...@freedesktop.org> wrote:
>> On 02/08/2017 10:26 AM, Nicolai Hähnle wrote:
>>> On 07.02.2017 23:54, Matt Turner wrote:
>>>> On Tue,
On Thu, Feb 9, 2017 at 3:22 PM, Matt Turner <matts...@gmail.com> wrote:
> On Thu, Feb 9, 2017 at 1:35 PM, Emil Velikov <emil.l.veli...@gmail.com> wrote:
>> From: Emil Velikov <emil.veli...@collabora.com>
>>
>> The two symbols referenced were introduced with v
On Thu, Feb 9, 2017 at 1:35 PM, Emil Velikov wrote:
> From: Emil Velikov
>
> Macro will always be defined as of earlier commit.
Same comment as 04/10.
___
mesa-dev mailing list
On Thu, Feb 9, 2017 at 1:35 PM, Emil Velikov wrote:
> From: Emil Velikov
>
> Macro will always be defined as of earlier commit.
How about something like
DRI2DriverPrimeShift was added in dri2proto-2.8, which we now require
as of the
On Thu, Feb 9, 2017 at 1:35 PM, Emil Velikov <emil.l.veli...@gmail.com> wrote:
> From: Emil Velikov <emil.veli...@collabora.com>
>
> The two symbols referenced were introduced with v2.2 and 2.3 of
> the dri2proto package.
... and we require dri2proto >= 2.6.
Revi
On Wed, Feb 8, 2017 at 6:03 PM, Marek Olšák wrote:
> From: Paul Berry
>
> This is not yet used in the build, just generated.
>
> v2: Add missing build dependencies.
> v3: Avoid mixing declarations and code, remove logic for avoiding emitting
> code
On Wed, Feb 8, 2017 at 11:38 AM, Bas Nieuwenhuizen
<b...@basnieuwenhuizen.nl> wrote:
> On Wed, Feb 8, 2017, at 11:25, Matt Turner wrote:
>> On Wed, Feb 8, 2017 at 12:31 AM, Timothy Arceri <t_arc...@yahoo.com.au>
>> wrote:
>> > On Tue, 2017-02-07 at 23:58 +0100,
On Wed, Feb 8, 2017 at 12:31 AM, Timothy Arceri <t_arc...@yahoo.com.au> wrote:
> On Tue, 2017-02-07 at 23:58 +0100, Matt Turner wrote:
>> On Tue, Feb 7, 2017 at 4:42 AM, Timothy Arceri <tarc...@itsqueeze.com
>> > wrote:
>> > This series adds support for
On Tue, Feb 7, 2017 at 4:42 AM, Timothy Arceri wrote:
> This series adds support for a GLSL IR level and TGSI (OpenGL/st)
> level caches.
>
> There are a few small bug fixes and a little bit of restructuring
> to the GLSL IR patches to make things work for Gallium drivers
On Tue, Feb 7, 2017 at 10:56 AM, Marek Olšák wrote:
> On Tue, Feb 7, 2017 at 2:57 AM, Kenneth Graunke wrote:
>> On Monday, February 6, 2017 8:54:40 PM PST Marek Olšák wrote:
>>> On Mon, Feb 6, 2017 at 8:20 PM, Ernst Sjöstrand wrote:
>>>
On Mon, Feb 6, 2017 at 3:02 PM, Emil Velikov wrote:
> The third release candidate for Mesa 17.0.0 is now available.
>
> Note that we have a couple of issues that I'd like to see fixed.
> If those are be not sorted by this Friday the final release will be
> out,
On Fri, Feb 3, 2017 at 5:37 PM, Jason Ekstrand wrote:
> On Thu, Feb 2, 2017 at 11:18 PM, Ben Widawsky wrote:
>> s/Sky Lake/Skylake/g
>
>
> I can never figure out which it's supposed to be. The PRM says "Skylake"
> but I thought ARC said "Sky Lake" but,
Previously if you used MESA_GL_VERSION_OVERRIDE=3.3COMPAT, Mesa exposed
an OpenGL 3.3 compatibility profile context (with various unimplemented
features and bugs), but still refused to compile shaders with
#version 330 compatibility
This patch simply adds a small bit of plumbing to let that
On Sun, Jan 29, 2017 at 8:29 PM, Kenneth Graunke <kenn...@whitecape.org> wrote:
> On Sunday, January 29, 2017 6:20:10 PM PST Matt Turner wrote:
>> This partially reverts commit 97217a40f97cdeae0304798b607f704deb0c3558.
>> It leaves ES 2.0 support in place per Ian's sugge
This partially reverts commit 97217a40f97cdeae0304798b607f704deb0c3558.
It leaves ES 2.0 support in place per Ian's suggestion, because ES 2.0
is designed to work on hardware like i915.
The piglit results look like:
name: before-revert-i915 after-revert-i915
On Fri, Jan 27, 2017 at 2:18 PM, Jason Ekstrand wrote:
> This causes hangs on Broadwell if you try to render to it. I have no
> idea how we managed to not hit this earlier.
>
> Cc: "13.0 17.0"
> ---
> src/intel/isl/isl_format.c | 5 +++--
On Thu, Jan 26, 2017 at 10:27 AM, Emil Velikov wrote:
> With this in mind we can drop the LLVM requirement, which some
> builders/distros explicitly patch out.
Like who?
I'm not sure why binary distros would do such a thing. Gentoo used to
have a patch that removed the
Cc: Dave Airlie <airl...@redhat.com>
> Cc: Bas Nieuwenhuizen <b...@basnieuwenhuizen.nl>
> Cc: Matt Turner <matts...@gmail.com>
> Cc: 17.0 <mesa-sta...@lists.freedesktop.org>
> Signed-off-by: Emil Velikov <emil.veli...@collabora.com>
> ---
> Fixing ANV a
Reported against 17.0.0-rc2 [1], but occurs on master as well
Reproduce with
./configure --with-dri-drivers= --with-gallium-drivers=swrast
--disable-gallium-llvm --enable-gallium-osmesa
Fails linking Gallium OSMesa with undefined references to draw_llvm_destroy.
I ran into this with mesa-17.0.0_rc2. This patch should go into the 17.0 branch.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Thu, Jan 26, 2017 at 10:11 AM, Eric Engestrom
<eric.engest...@imgtec.com> wrote:
> This is git, not svn :P
>
> Signed-off-by: Eric Engestrom <eric.engest...@imgtec.com>
Reviewed-by: Matt Turner <matts...@gmail.com>
> ---
> I also noticed some differe
On Thu, Jan 26, 2017 at 10:22 AM, Jason Ekstrand wrote:
> Ugh... windows defines long to be 32-bit on 32-bit platforms Yeah.
long is 32-bit on 32-bit x86/Linux too...
I think you mean they define long to be 32-bits on 64-bit platforms.
On Mon, Jan 23, 2017 at 4:54 PM, Matt Turner <matts...@gmail.com> wrote:
> These files belong to the vulkan loader.
I forgot to add the tag, but this (commit 045f38a5075) should go to
the 17.0 branch. Emil, can you see to that?
___
mesa-dev mai
To make distributions lives easier, can we please support llvm-4.0 in
the mesa-13.0 branch?
It currently fails to compile:
https://bugs.gentoo.org/show_bug.cgi?id=606608
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
On Tue, Jan 24, 2017 at 2:18 PM, Kenneth Graunke wrote:
> SIMD16 compute shaders use a send(16) with mlen 1 for the EOT message,
> using a source of g127 for the single register. With a UD type, this
> supposedly could read g128, which doesn't exist, causing the simulator
On Tue, Jan 24, 2017 at 8:41 AM, Emil Velikov <emil.l.veli...@gmail.com> wrote:
> On 24 January 2017 at 00:54, Matt Turner <matts...@gmail.com> wrote:
>> These files belong to the vulkan loader.
> Fully agreed, patch is
> Reviewed-by: Emil Velikov <emil.veli...@coll
These files belong to the vulkan loader.
---
src/intel/vulkan/Makefile.am | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/src/intel/vulkan/Makefile.am b/src/intel/vulkan/Makefile.am
index fba3d66..95f276e 100644
--- a/src/intel/vulkan/Makefile.am
+++
On Mon, Jan 23, 2017 at 2:59 AM, Samuel Iglesias Gonsálvez
<sigles...@igalia.com> wrote:
> On Fri, 2017-01-20 at 14:25 -0800, Francisco Jerez wrote:
>> Matt Turner <matts...@gmail.com> writes:
>>
>> > In commit c35fa7a, we changed the "width"
Thanks Sam!
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Thu, Jan 19, 2017 at 9:47 PM, Jason Ekstrand wrote:
> This gets the UE4 bitfield_extract optimization working again. It had
> stopped working due to the constant 0xff00ff00 getting sign-extended
> when it shouldn't have.
Wait, what? When did it get broken?
Elsewhere we use _TOK. Not sure if you want to move to _TOKEN everywhere.
Reviewed-by: Matt Turner <matts...@gmail.com>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Gen8 adds Q/UQ types. We attempted to change the types back to DF in the
generator (commit c95380c40), but an assertion added in the FP64 series
(commit e481dcc3) triggers before that code has a chance to execute.
In fact, using Q/UQ in the IR and then changing to DF in the generator
would not
This reverts commit c95380c4044237d73fb537511667c3c8f658fcee.
---
src/mesa/drivers/dri/i965/brw_eu_emit.c | 8
1 file changed, 8 deletions(-)
diff --git a/src/mesa/drivers/dri/i965/brw_eu_emit.c
b/src/mesa/drivers/dri/i965/brw_eu_emit.c
index 4b557d9..de6a1d9 100644
---
On Tue, Jan 17, 2017 at 1:49 AM, Samuel Iglesias Gonsálvez
wrote:
> It is tested empirically that IVB/BYT don't support indirect addressing
> with doubles but it is not documented in the PRM.
>
> This patch applies the same solution than for Cherryview/Broxton and
> takes
Otherwise for a pack_double_2x32_split opcode, we emit:
vec1 64 ssa_135 = pack_double_2x32_split ssa_133, ssa_134
mov(8) g5<1>UD g5<4>.xUD { align16 1Q
compacted };
mov(8) g7<2>UD g5<4,4,1>UD { align1 1Q };
On IVB/BYT, region parameters and execution size for DF are in terms of
32-bit elements, so they are doubled. For evaluating the validity of an
instruction, we halve them.
---
src/mesa/drivers/dri/i965/brw_eu_validate.c | 12
1 file changed, 12 insertions(+)
diff --git
I committed my EU validator earlier today. It's caught three bugs in the IVB
fp64 series. Patches 2 and 3 fix two of them. I'll respond directly to the
patch in Igalia's series that introduces the other bug.
These should go in with Igalia's series, before the extension is turned on.
In commit c35fa7a, we changed the "width" of DF source registers to 2,
which is conceptually fine. Unfortunately a VertStride of 2 is not
allowed by align16 instructions on IVB/BYT, and the regular VertStride
of 4 works fine in any case.
See
On Thu, Jan 19, 2017 at 4:50 AM, Samuel Iglesias Gonsálvez
wrote:
> As we are blocking the release and there more patches for review,
> another possibility is to land this patch [2] (replacing this patch)
> and then fix it later to not block Mesa 17.0 release more than
On Wed, Jan 18, 2017 at 2:45 AM, Samuel Iglesias Gonsálvez
<sigles...@igalia.com> wrote:
> On Tue, 2017-01-17 at 13:33 -0800, Francisco Jerez wrote:
>> Samuel Iglesias Gonsálvez <sigles...@igalia.com> writes:
>>
>> > From: Matt Turner <matts...@gmail.com>
On Tue, Jan 17, 2017 at 1:33 PM, Francisco Jerez <curroje...@riseup.net> wrote:
> Samuel Iglesias Gonsálvez <sigles...@igalia.com> writes:
>
>> From: Matt Turner <matts...@gmail.com>
>>
>> On HSW+, scalar DF sources can be accessed using the normal <0,
On Tue, Jan 17, 2017 at 2:38 PM, Francisco Jerez <curroje...@riseup.net> wrote:
> Matt Turner <matts...@gmail.com> writes:
>
>> On Tue, Jan 17, 2017 at 11:40 AM, Francisco Jerez <curroje...@riseup.net>
>> wrote:
>>> Kenneth Graunke <kenn...@whit
On Tue, Jan 17, 2017 at 1:01 PM, Timothy Arceri
wrote:
> This number was chosen in an attempt to match the limits applied to
> GLSL IR.
>
> A recent attempt to disable the GLSL IR optimisation loop in the i965
> backend resulted in 4 loops from The Talos Principle
On Tue, Jan 17, 2017 at 11:40 AM, Francisco Jerez <curroje...@riseup.net> wrote:
> Kenneth Graunke <kenn...@whitecape.org> writes:
>
>> (Co-authored by Matt Turner.)
>>
>> Image atomics, for example, return a value - but the shader may not
>> want to use i
On Thu, Jan 5, 2017 at 5:07 AM, Samuel Iglesias Gonsálvez
wrote:
> From: "Juan A. Suarez Romero"
>
> When splitting a CMP/MOV instruction with NULL dest, DF sources, and
> conditional modifier; we can't use directly the flag registers, as they will
>
we've reached the top of the mountain.
Reviewed-by: Matt Turner <matts...@gmail.com>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Thu, Jan 5, 2017 at 5:07 AM, Samuel Iglesias Gonsálvez
wrote:
> From: "Juan A. Suarez Romero"
>
> When lowering double_to_single() we added a final mov() that puts 32-bit
I can't confirm that this patch is necessary in the current
On Thu, Jan 5, 2017 at 5:07 AM, Samuel Iglesias Gonsálvez
wrote:
> From: "Juan A. Suarez Romero"
>
> When spliting double_to_single() in Ivybridge/Valleyview, the second
> part should use a temporal register, and then move the values to the
> second
On Thu, Jan 5, 2017 at 5:07 AM, Samuel Iglesias Gonsálvez
wrote:
> From: "Juan A. Suarez Romero"
>
> In the generator we must generate slightly different code for
> Ivybridge/Valleview, because of the way the stride works in
> this hardware.
> ---
>
ide
effect of this is that we can simplify VEC4_OPCODE_TO_DOUBLE.
From 5637d035982c89415d47be119ad6a1c9d2e14e42 Mon Sep 17 00:00:00 2001
From: Matt Turner <matts...@gmail.com>
Date: Thu, 12 Jan 2017 18:05:58 -0800
Subject: [PATCH] i965: Use source region <1,2,0> when converting to DF.
Doing so allows us to u
On Fri, Jan 13, 2017 at 1:01 PM, Vladislav Egorov wrote:
> 2017-01-13 22:43 GMT+03:00 Emil Velikov :
>>
>> On 13 January 2017 at 19:22, Vladislav Egorov wrote:
>> > 13.01.2017 19:51, Emil Velikov пишет:
>> >>
>> >> From: Emil
I am generally in favor of this for all the reasons you've described.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Fri, Jan 13, 2017 at 12:39 PM, Ben Crocker wrote:
> Reenable the PPC64LE Vector-Scalar Extension for LLVM versions >= 3.8.1,
> now that LLVM bug 26775 and its corollary, 25503, are fixed.
>
> Signed-off-by: Ben Crocker
> ---
>
On Fri, Jan 13, 2017 at 11:51 AM, Dylan Baker wrote:
> Quoting Emil Velikov (2017-01-13 08:51:31)
>> From: Emil Velikov
>>
>> At the moment we support 5+ different implementations each with varying
>> amount of bugs - from thread safely problems
On Fri, Jan 13, 2017 at 10:04 AM, Elie Tournier wrote:
> Use the binary to run shader-db instead of run.py
>
> Signed-off-by: Elie Tournier
> ---
> README | 18 --
> 1 file changed, 16 insertions(+), 2 deletions(-)
>
> diff --git
On Thu, Jan 12, 2017 at 4:56 PM, Ilia Mirkin <imir...@alum.mit.edu> wrote:
> On Thu, Jan 12, 2017 at 7:46 PM, Matt Turner <matts...@gmail.com> wrote:
>> On Thu, Jan 12, 2017 at 3:20 PM, Ilia Mirkin <imir...@alum.mit.edu> wrote:
>>> On Thu, Jan 12, 20
On Thu, Jan 12, 2017 at 3:20 PM, Ilia Mirkin wrote:
> On Thu, Jan 12, 2017 at 6:04 PM, Nicolai Hähnle wrote:
>> On 12.01.2017 23:46, Ilia Mirkin wrote:
>>>
>>> On Thu, Jan 12, 2017 at 4:03 PM, Matteo Bruni
>>> wrote:
On Thu, Jan 5, 2017 at 5:07 AM, Samuel Iglesias Gonsálvez
wrote:
> We need to split DF instructions in two on IVB/VLV as it needs an
> execsize 8 to process 4 DF values (one GRF in total).
>
> Signed-off-by: Samuel Iglesias Gonsálvez
> ---
>
On Thu, Jan 5, 2017 at 5:07 AM, Samuel Iglesias Gonsálvez
wrote:
> From: "Juan A. Suarez Romero"
>
s/MOVE_INDIRECT/MOV_INDIRECT/ in the subject
> Previous to Broadwell, we have 8 registers for MOV_INDIRECT. But if
> IVB/VLV deal with DFs, we will
On Thu, Jan 5, 2017 at 5:07 AM, Samuel Iglesias Gonsálvez
wrote:
> From: "Juan A. Suarez Romero"
>
> When converting a DF to F, we set dst stride to 2, to fulfil alignment
> restrictions.
>
> But in IVB/VLV, this is not necessary, as each DF conversion
On Thu, Jan 5, 2017 at 5:07 AM, Samuel Iglesias Gonsálvez
wrote:
> From: "Juan A. Suarez Romero"
>
> The execution data size is the biggest type size of any instruction
> operand.
>
> We will use it to know if the instruction deals with DF, because in
depth <
>state->blocks[best->index].loop_depth)
> - best = lca;
> - lca = lca->imm_dom;
> + best = block;
> +
> + if (block == def->parent_instr->block)
> + break;
> }
I had to come up wit
Reviewed-by: Matt Turner <matts...@gmail.com>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
On Thu, Jan 12, 2017 at 3:24 AM, Juan A. Suarez Romero
wrote:
> This fixes a defect detected by Coverity Scan.
> ---
> src/mesa/drivers/dri/i965/brw_draw_upload.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/src/mesa/drivers/dri/i965/brw_draw_upload.c
>
901 - 1000 of 6330 matches
Mail list logo