Clang tryed to declare the non type member of struct module (enum type type)
(in clover/core/module.hpp) instead of a variable of type enum (enum type).
Signed-off-by: Albert Freeman
---
src/gallium/state_trackers/clover/llvm/invocation.cpp | 2 +-
1 file changed, 1 insertion(+), 1 deletion
year.month or year.dayoutofdaysthatyear
dayoutoofdaysthatyear skips lots of integers quickly: reducing
confusion of where is release x.(y - something) and better handles
quick fix releases
but makes it harder to determine how far into the year the release is
although with some effort can be conver
remember which years are quaterly.
Though I am just trying to help, I personally don't care what release
system is chosen, so you need not take my opinion into consideration.
On 3 October 2016 at 09:40, Jason Ekstrand wrote:
>
> On Oct 3, 2016 12:19 AM, "Albert Freem
It might be a good idea to consider moving the nir -> llvm code out of
the amd folder for reuse by a Vulkan software rasterizer or something.
I have heard another developers recent interest in developing a Vulkan
software rasterizer. I at one stage was interested in developing a
Vulkan software ras
I wrote this code in response to a issue someone on mesa-users had
(https://lists.freedesktop.org/archives/mesa-users/2016-October/001231.html).
They didn't reply so I don't know if the patch resolved the issue. Can
someone please determine its usefulness. Also please check if
drmCommandWrite() is
A different patch to that code has been applied that does the same
thing in a different (better) way.
On 24 November 2016 at 05:25, Albert Freeman wrote:
> I wrote this code in response to a issue someone on mesa-users had
> (https://lists.freedesktop.org/archives/mesa-users/2016-October/
Removed reference to unused header file to reduce src/mesa/main dependency on
src/mesa/drivers.
Signed-off-by: Albert Freeman
---
I do not have commit access!
No regressions with piglit (tests/quick.py).
src/mesa/main/enable.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/src/mesa
The reply from Eric Anholt made two suggestions that should not be
difficult to implement for someone who made the patch in the first
place. Why would code be committed when improvements could be easily
made? From what I have seen, this kind of thing happens even to
experienced mesa developers who
Maybe we should add some kind of prefix to this to indicate a
performance vs security trade off and a more powerful general overide
option to enable/disable all such future flags?
On 4 September 2015 at 09:39, Jeremy Huddleston Sequoia
wrote:
> Wow, that's a blast from the past ;)
>
>> On Sep 3,
knowledge.
2. We can't just automatically commit patches for security reasons
(best not to mention).
3. Whether committers would even like to make any changes.
On 6 September 2015 at 08:28, Lauri Kasanen wrote:
> On Sat, 5 Sep 2015 23:29:05 +
> Albert Freeman wrote:
>
>> Th
er 2015 at 11:42, Albert Freeman wrote:
> Ah, okay. I see what you mean now (i.e. you had to wait three months
> for those suggestions I mentioned). I still haven't recieved a
> response at all for my first patch from almost a year ago (although it
> was insanely tri
Correction, we just need someone to mark all the comitted patches in
patchwork so that we can easily pick out the ones with issues.
On 7 September 2015 at 04:56, Albert Freeman wrote:
> Oops, my "plan" focuses on patches that have nothing wrong with them,
> instead of patches tha
On 7 September 2015 at 08:22, Emil Velikov wrote:
> On 7 September 2015 at 05:59, Albert Freeman
> wrote:
>> Correction, we just need someone to mark all the comitted patches in
>> patchwork...
> This is already done automatically.
>
> Sigh top posting :'(.
>
On 8 September 2015 at 01:16, Albert Freeman wrote:
> On 7 September 2015 at 08:22, Emil Velikov wrote:
>> On 7 September 2015 at 05:59, Albert Freeman
>> wrote:
>>> Correction, we just need someone to mark all the comitted patches in
>>> patchwork...
>
"enum type".
Replaced "typename" with "enum" to force clang to declare the variable
marg_type with type "enum type" of module::argument.
CC: "11.0"
Reviewed-by: Francisco Jerez
Signed-off-by: Albert Freeman
---
src/gallium/state_trackers/clover/l
Reviewed-by: Albert Freeman
On 10 September 2015 at 15:03, Brian Paul wrote:
> An unsigned int is always >= 0. Found with Coverity.
> ---
> src/gallium/winsys/svga/drm/vmw_context.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/src/gallium/winsys/svga/drm/v
FFER)
> #define LLVM_R600_BUFFER_INFO_CONST_BUFFER \
> (CONSTANT_BUFFER_0_ADDR_SPACE + R600_BUFFER_INFO_CONST_BUFFER)
>
> --
> 2.5.1
>
> ___
> mesa-dev mailing list
> mesa-dev@lists.fre
On 26 September 2015 at 03:32, Ilia Mirkin wrote:
> Hi Ian (and other spec experts),
>
> The ARB_ssbo spec mentions the following:
>
> OpenGL 4.0 (either core or compatibility profile) is required.
>
> ...
>
> Additionally, the shading language provides the memoryBarrier() function
> t
On 27 September 2015 at 08:30, Ilia Mirkin wrote:
> On Sat, Sep 26, 2015 at 6:12 PM, Albert Freeman
> wrote:
>> On 26 September 2015 at 03:32, Ilia Mirkin wrote:
>>> Hi Ian (and other spec experts),
>>>
>>> The ARB_ssbo spec mentions the following:
On 27 September 2015 at 08:32, Albert Freeman wrote:
> On 27 September 2015 at 08:30, Ilia Mirkin wrote:
>> On Sat, Sep 26, 2015 at 6:12 PM, Albert Freeman
>> wrote:
>>> On 26 September 2015 at 03:32, Ilia Mirkin wrote:
>>>> Hi Ian (and other spec experts),
On 27 September 2015 at 03:46, Ilia Mirkin wrote:
> Found by Coverity
>
> Signed-off-by: Ilia Mirkin
> ---
> src/gallium/auxiliary/util/u_blitter.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/gallium/auxiliary/util/u_blitter.c
> b/src/gallium/auxiliary/util/u_bl
On 27 September 2015 at 09:35, Ilia Mirkin wrote:
> On Sat, Sep 26, 2015 at 7:29 PM, Albert Freeman
> wrote:
>> On 27 September 2015 at 03:46, Ilia Mirkin wrote:
>>> Found by Coverity
>>>
>>> Signed-off-by: Ilia Mirkin
>>> ---
>>>
Reviewed-by: Albert Freeman
On 27 September 2015 at 09:41, Albert Freeman wrote:
> On 27 September 2015 at 09:35, Ilia Mirkin wrote:
>> On Sat, Sep 26, 2015 at 7:29 PM, Albert Freeman
>> wrote:
>>> On 27 September 2015 at 03:46, Ilia Mirkin wrote:
>>>> Fo
top of your patch against mesa git):
diff --git a/src/gallium/state_trackers/dri/dri2.c
b/src/gallium/state_trackers/dri/dri2.c
index ab940e4..712203b 100644
--- a/src/gallium/state_trackers/dri/dri2.c
+++ b/src/gallium/state_trackers/dri/dri2.c
@@ -1338,6 +1338,7 @@ dri2_get_fence_from_cl_ev
:
> NULL,
> dri2_sync->fence, wait_flags,
> timeout))
>dri2_sync->base.SyncStatus = EGL_SIGNALED_KHR;
> --
> 2.1.4
>
> ___
> mesa-dev mailing list
&
On 27 September 2015 at 03:21, Mauro Rossi wrote:
> Hi,
>
> Marek's patches solved Camera and Youtube crashes on nouveau and radeonsi.
> I'm available to test on i965, if needed
>
> I think at this point the remaining major problem for lollipop-x86 is the
> font artifacts/invisible chars on i965GM
> parts of GL_ARB_gpu_shader5, which is done for some drivers)
>GL_OES_primitive_bounding boxnot started
> --
> 2.5.3
>
> ___
> mesa-dev mailing list
> mesa-dev@lists.freedesktop.org
> http://lists.freedeskto
On 28 September 2015 at 04:12, Emil Velikov wrote:
> On 26 September 2015 at 00:49, Marek Olšák wrote:
>> From: Marek Olšák
>>
>> The spec doesn't require it. This fixes a crash on Android.
>>
> Nicely spotted Marek.
>
> A couple of related (not supposed to be part of this patch) notes:
> - Thi
On 28 September 2015 at 14:38, Albert Freeman wrote:
> On 28 September 2015 at 04:12, Emil Velikov wrote:
>> On 26 September 2015 at 00:49, Marek Olšák wrote:
>>> From: Marek Olšák
>>>
>>> The spec doesn't require it. This fixes a crash on Android.
&g
On 28 September 2015 at 15:20, Albert Freeman wrote:
> On 28 September 2015 at 14:38, Albert Freeman
> wrote:
>> On 28 September 2015 at 04:12, Emil Velikov wrote:
>>> On 26 September 2015 at 00:49, Marek Olšák wrote:
>>>> From: Marek Olšák
>>>>
&
On 28 September 2015 at 08:10, Marek Olšák wrote:
> On Mon, Sep 28, 2015 at 7:20 AM, Albert Freeman
> wrote:
>> On 28 September 2015 at 14:38, Albert Freeman
>> wrote:
>>> On 28 September 2015 at 04:12, Emil Velikov
>>> wrote:
>>>> O
On 29 September 2015 at 07:25, Albert Freeman wrote:
> On 28 September 2015 at 08:10, Marek Olšák wrote:
>> On Mon, Sep 28, 2015 at 7:20 AM, Albert Freeman
>> wrote:
>>> On 28 September 2015 at 14:38, Albert Freeman
>>> wrote:
>>>> On 28 Septe
On 28 September 2015 at 20:25, Marek Olšák wrote:
> On Mon, Sep 28, 2015 at 10:19 PM, Chad Versace wrote:
>> On Fri 25 Sep 2015, Chih-Wei Huang wrote:
>>> CC to mesa-dev for help.
>>>
>>> 2015-09-25 22:12 GMT+08:00 Chih-Wei Huang :
>>> > 2015-09-25 16:21 GMT+08:00 Chih-Wei Huang :
>>> >> Actually
On 29 September 2015 at 07:28, Albert Freeman wrote:
> On 29 September 2015 at 07:25, Albert Freeman
> wrote:
>> On 28 September 2015 at 08:10, Marek Olšák wrote:
>>> On Mon, Sep 28, 2015 at 7:20 AM, Albert Freeman
>>> wrote:
>>>> On 28 September
On 29 September 2015 at 15:01, Marek Olšák wrote:
> On Tue, Sep 29, 2015 at 4:54 PM, Albert Freeman
> wrote:
>> On 29 September 2015 at 07:28, Albert Freeman
>> wrote:
>>> On 29 September 2015 at 07:25, Albert Freeman
>>> wrote:
>>>> O
On 29 September 2015 at 14:48, Romain Failliot
wrote:
> What I don't understand is that all the lines starting with a "-" seems to
> be part of the GL_ARB_gpu_shader5 extension. See the line here:
> http://cgit.freedesktop.org/mesa/mesa/tree/docs/GL3.txt#n99
>
> If I'm right, it means that, consid
On 23 November 2015 at 03:17, Ilia Mirkin wrote:
> On Sun, Nov 22, 2015 at 9:28 PM, Dave Airlie wrote:
>> From: Dave Airlie
>>
>> No reason not to build this, it has no external
>> requirements at the moment.
>
> Not that I object, but what's the policy around these defaults? Should
> we also ad
37 matches
Mail list logo
