<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - HAVE_LLVM undelcared in r600_pipe_common.c if enable_r600_llvm not set"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88209#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - HAVE_LLVM undelcared in r600_pipe_common.c if enable_r600_llvm not set"
href="https://bugs.freedesktop.org/show_bug.cgi?id=88209">bug 88209</a>
from <span class="vcard"><a class="email" href="mailto:athomas@synexxus.com" title="athomas@synexxus.com">athomas@synexxus.com</a>
</span></b>
<pre>The patch seems to be in the right direction of removing the dependance of
LLVM in the source code, but I dont have hardware to test functionality. I can
test that it compiles when LLVM isn't specified on Monday. I don't have enough
knowledge on the internal workings of the driver to make comments on the
implications of the code chages though.
A couple of notes I meant to add last night:
Build Environment:
- Building directly on an ARM platform. imx6 - very similar to sabrelite.
- I set the prefix to be someplace in my /home directory via the X.org build.sh
script.
- Flags: --enable-driglx-direct --enable-gles1 --enable-gles2 --enable-glx
--with-dri-drivers=radeon
Additional notes about the mesa build with llvm:
Normally the auto setting for enable_gallium_llvm will set
enable_gallium=llvm=yes and trigger llvm to be used with the driver. This is
NOT the case if the host CPU is not i*86/x96_64/AMD64. See the current snippet
below from configure.ac
if test "x$enable_gallium_llvm" = xauto; then
case "$host_cpu" in
i*86|x86_64|amd64) enable_gallium_llvm=yes;;
esac
fi
Tests I did:
- I hacked the configure.ac to always set enable_gallium_llvm=yes and was able
to get the gallium r600 driver to build and subsquently mesa.
- I, somewhat stupidly, tested --with-dri-drivers=nouveau and not
--with-gallium-drivers=nouveau because I dont care about the drivers - I will
end up using Freescale/Vivante drivers. BUT - can the two be aligned or at
least checked for inconsistencies.
Questions:
- Does it make sense to migrate the default to use LLVM for ARM platforms?
At the end of the day I didnt really care about the drivers themselves because
I will be dropping in Vivante drivers via Freescale, but I needed mesa/gallium
to build. I should have cut the gallium drivers out, but I was concerned I had
my build environment/paths setup correctly.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>