Ian, does this version get your R-b?
On Tue, 2015-01-20 at 17:07 +0100, Iago Toral Quiroga wrote:
> v2 (Ian Romanick)
> - Move the check to the lexer before rallocing a copy of the large string.
>
> Fixes the following 2 dEQP tests:
> dEQP-GLES3.functional.shaders.keywords.invalid_identifiers.max
From: Marius Predut
On 32-bit, for floating point operations is used x86 FPU registers instead SSE,
reason for when reinterprets an integer as a float result is unexpected
(modify floats when they are written to memory).
The defect was checked with and without -O3 compiler flag.
CC:
Bugzilla:
Fixes compilation with musl libc.
Reviewed-by: Ian Romanick
---
Changes in v2: Add comment by Ian Romanick on fpclassify in C99
---
src/mesa/main/querymatrix.c | 18 +++---
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/src/mesa/main/querymatrix.c b/src/mesa/main/quer
On Sun, Jan 25, 2015 at 8:56 AM, Connor Abbott wrote:
> Unlike with non-SSA ALU instructions, where if they're per-component
> you have to look at the writemask to know which source channels are
> being used, SSA ALU instructions always have all the possible channels
> enabled so we can just look
https://bugs.freedesktop.org/show_bug.cgi?id=88783
--- Comment #2 from Jan Vesely ---
Created attachment 112818
--> https://bugs.freedesktop.org/attachment.cgi?id=112818&action=edit
Fix build after 226981
(In reply to Kai from comment #1)
> (In reply to Kai from comment #0)
> > With LLVM > r22
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=88783
Signed-off-by: Jan Vesely
---
src/gallium/state_trackers/clover/llvm/invocation.cpp | 4
1 file changed, 4 insertions(+)
diff --git a/src/gallium/state_trackers/clover/llvm/invocation.cpp
b/src/gallium/state_trackers/clover/llvm/
Before, we were only copying the first N channels, where N is the size
of the SSA destination, which is fine for per-component instructions,
but non-per-component instructions like fdot3 can have more source
components than destination components. Fix this using the helper
function introduced in th
Unlike with non-SSA ALU instructions, where if they're per-component
you have to look at the writemask to know which source channels are
being used, SSA ALU instructions always have all the possible channels
enabled so we can just look at the number of components in the SSA
definition for per-compo
Jan Vesely writes:
> On Sun, 2015-01-25 at 01:02 +0100, Niels Ole Salscheider wrote:
>> On Saturday 24 January 2015, 18:24:16, Jan Vesely wrote:
>> > On Sat, 2015-01-24 at 22:49 +0100, Niels Ole Salscheider wrote:
>> > > Since 8e7df519bd8556591794b2de08a833a67e34d526, we initialise all targets
>>
On Sun, 2015-01-25 at 01:02 +0100, Niels Ole Salscheider wrote:
> On Saturday 24 January 2015, 18:24:16, Jan Vesely wrote:
> > On Sat, 2015-01-24 at 22:49 +0100, Niels Ole Salscheider wrote:
> > > Since 8e7df519bd8556591794b2de08a833a67e34d526, we initialise all targets
> > > in clover. This fixes
https://bugs.freedesktop.org/show_bug.cgi?id=88766
--- Comment #7 from Francisco Jerez ---
(In reply to Ilia Mirkin from comment #6)
> (In reply to Francisco Jerez from comment #5)
> > Most likely this bug is not caused by the Clang compiler itself, but by
> > the standard library implementation.
https://bugs.freedesktop.org/show_bug.cgi?id=88783
--- Comment #1 from Kai ---
(In reply to Kai from comment #0)
> With LLVM > r226934 I get the following build error in a clean chroot build
Small clarification: SVN r226934 was my last successful build. I saw the
failure with r227016. Somewhere
https://bugs.freedesktop.org/show_bug.cgi?id=88783
Bug ID: 88783
Summary: FTBFS: Clover:
src/gallium/state_trackers/clover/llvm/invocation.cpp:
335:49: error: no matching function for call to
'llvm::TargetLibraryInf
https://bugs.freedesktop.org/show_bug.cgi?id=77449
Kai changed:
What|Removed |Added
Depends on||88781
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=77449
Kai changed:
What|Removed |Added
Depends on||88780
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=69874
--- Comment #12 from Kai ---
Just to note the progress here: my latest build of Mesa (d2811c29da) shows this
warning for only one directory. Seems like Mesa is almost there to be Automake
1.14 ready. ;-)
--
You are receiving this mail because:
16 matches
Mail list logo