dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88209] HAVE_LLVM undelcared in r600_pipe_common.c if enable_r600_llvm not set
Date: Fri, 09 Jan 2015 14:25:34 +0000	[thread overview]
Message-ID: <bug-88209-502-YuckTo3d8g@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-88209-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2055 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=88209

--- Comment #3 from athomas@synexxus.com ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2864 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-01-09 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-88209-502@http.bugs.freedesktop.org/>
2015-01-08 18:21 ` [Bug 88209] HAVE_LLVM undelcared in r600_pipe_common.c if enable_r600_llvm not set bugzilla-daemon
2015-01-09  9:53 ` bugzilla-daemon
2015-01-09 14:25 ` bugzilla-daemon [this message]
2015-01-23 21:51 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-88209-502-YuckTo3d8g@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox