From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66847] New: compilation broken with llvm 3.3
Date: Fri, 12 Jul 2013 09:21:36 +0000 [thread overview]
Message-ID: <bug-66847-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2026 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66847
Priority: medium
Bug ID: 66847
Assignee: dri-devel@lists.freedesktop.org
Summary: compilation broken with llvm 3.3
Severity: normal
Classification: Unclassified
OS: All
Reporter: marvin24@gmx.de
Hardware: Other
Status: NEW
Version: 9.1
Component: Drivers/Gallium/r600
Product: Mesa
r600 build is broken in 9.1 (stable branch) when using llvm 3.3 (also stable).
I got it compiling with
0ee3cc5 r600g: Add $(DEFINES) to AM_CXXFLAGS
3a11b9b radeon/llvm: remove uneeded inclusion
1d16c20 radeon/llvm: Fix build with LLVM 3.3
from upstream plus
--- a/src/gallium/drivers/r600/llvm_wrapper.cpp
+++ b/src/gallium/drivers/r600/llvm_wrapper.cpp
@@ -2,11 +2,13 @@
#include <llvm/ADT/StringRef.h>
#if HAVE_LLVM < 0x0303
#include <llvm/LLVMContext.h>
+#include <llvm/Support/IRReader.h>
#else
#include <llvm/IR/LLVMContext.h>
+#include <llvm/IRReader/IRReader.h>
+#include <llvm/IR/Module.h>
#endif
#include <llvm/PassManager.h>
-#include <llvm/Support/IRReader.h>
#include <llvm/Support/MemoryBuffer.h>
#include <llvm/Support/SourceMgr.h>
#include <llvm/Transforms/IPO.h>
but that doesn't seem to be sufficient because I get a lot of
EE r600_asm.c:2041 r600_bytecode_build - unsupported CF instruction
(0xFFFFFFFF)
EE r600_shader.c:160 r600_pipe_shader_create - building bytecode failed !
EE r600_state_common.c:756 r600_shader_select - Failed to build shader variant
(type=0) -22
EE r600_asm.c:2041 r600_bytecode_build - unsupported CF instruction
(0xFFFFFFFF)
EE r600_shader.c:160 r600_pipe_shader_create - building bytecode failed !
EE r600_state_common.c:756 r600_shader_select - Failed to build shader variant
(type=0) -22
messages (this was from glxgears).
I would be great if this could be fixed for Mesa-9.1.5 because many distros
will use it.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3399 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
next reply other threads:[~2013-07-12 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 9:21 bugzilla-daemon [this message]
2013-07-12 10:00 ` [Bug 66847] compilation broken with llvm 3.3 bugzilla-daemon
2013-07-12 10:26 ` bugzilla-daemon
2013-07-12 10:48 ` bugzilla-daemon
2013-07-12 11:01 ` bugzilla-daemon
2013-07-12 12:25 ` bugzilla-daemon
2013-07-12 12:29 ` bugzilla-daemon
2013-07-12 18:39 ` bugzilla-daemon
2013-07-19 15:27 ` 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-66847-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.