<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - OSMesa 17.1.3 simd16intrin build FAIL on Win/MinGW - 'expected initializer before _simd16_setzero_ps ...'"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101614">101614</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>OSMesa 17.1.3 simd16intrin build FAIL on Win/MinGW - 'expected initializer before _simd16_setzero_ps ...'
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>17.1
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>blocker
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/Gallium/swr
</td>
</tr>
<tr>
<th>Assignee</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>trevor.sandy@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>mesa-dev@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Please help ! My mesa build consistently fails at with the following log trace:
src/gallium/drivers/swr/rasterizer/common/simd16intrin.h:127:35: error:
expected initializer before '_simd16_setzero_ps'
SIMD16_EMU_AVX512_0(simd16scalar, _simd16_setzero_ps, _mm256_setzero_ps).
Builds on Linux and OSX are unaffected.
You can see a detailed install log output for Mesa 17.1.3 at
<a href="https://gist.github.com/trevorsandy/0f8f83a9f8963911d5a42f8723c772fb">https://gist.github.com/trevorsandy/0f8f83a9f8963911d5a42f8723c772fb</a> and the
same for 17.1.2 at
<a href="https://gist.github.com/trevorsandy/69d22f8a0ceeafe298baba9587cd37e9">https://gist.github.com/trevorsandy/69d22f8a0ceeafe298baba9587cd37e9</a>
I have been chasing this issue for the past week without success. I've read the
content at Mesa3D.org and search across the mail archives. I've also followed
the documented dev env requirements.
The gist URLs above provide a detailed capture of the installation output -
based on this customized install script.
<a href="https://github.com/trevorsandy/osmesa-install/blob/master/osmesa-install.sh">https://github.com/trevorsandy/osmesa-install/blob/master/osmesa-install.sh</a>.
This script can be used to reproduce this behaviour.
Here is the options section of logged output for Mesa 17.1.3:
Mesa build options for platform MINGW64_NT-10.0:
- build date: 28/06/2017 01:15:39
- release, non-debug build
- non-mangled
- swr Gallium renderer
- reuse built source at rebuild
- build llvm: No (Note: using llvm version 4.0.0 already built successfully)
- mesa version: 17.1.3
- osmesa prefix: /opt/osmesa
- glu version: 9.0.0
- execute osmesa demo: No
- CC: gcc
- CXX: g++
- CFLAGS: -O3
- CXXFLAGS: -O3
- msys version: 2017.05-1
- mingw version: 2.28-1
- gcc version: 6.3.0-1
- cmake version: 3.8.1-3
- scons version: 2.5.1-1
- bison/yacc version: 3.0.4-1
- python2 version: 2.7.13-1
- python2-mako version: 1.0.6-2
- libxml2 version: 2.9.2-3
- silent logging
- log file: /home/Trevor/Projects/osmesa-install/osmesa-install_27.log
* extracting Mesa...
* applying patches...
* applying patch add_pi.patch...
(Stripping trailing CRs from patch; use --binary to disable.)
patching file src/compiler/glsl/builtin_functions.cpp
Hunk #1 succeeded at 84 with fuzz 2 (offset 22 lines).
* applying patch gallium-osmesa-threadsafe.patch...
(Stripping trailing CRs from patch; use --binary to disable.)
patching file src/gallium/state_trackers/osmesa/osmesa.c
Hunk #16 succeeded at 881 (offset -1 lines).
* applying patch install-GL-headers.patch...
...
** Mesa scons command line arguments...
** env
** LLVM_CONFIG="/opt/llvm/bin/llvm-config.exe"
** LLVM="/opt/llvm"
** CFLAGS="-O3"
** CXXFLAGS="-O3 -std=c++11"
** LDFLAGS="-static -s"
** scons
** build="release"
** platform=windows
** toolchain=mingw
** machine="x86_64"
** texture_float=yes
** llvm="yes"
** swr="1"
** verbose=yes
** osmesa
...
Many thanks in advance.
Cheers,</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>