| Summary: | Beignet build failure with Blender (conflicts with mesa) | ||
|---|---|---|---|
| Product: | Beignet | Reporter: | Russell Palmer <russell.palmer> |
| Component: | Beignet | Assignee: | Zhigang Gong <zhigang.gong> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Russell Palmer
2015-02-25 21:29:13 UTC
You can try the following patch which should fix the build problem. But you may meet other problems after that if you continue to try blender, and you are welcome to file new bugs if so. Thanks. commit a9366a0e3b5f4bc1e9907ec165aecf741aa66a7c Author: Zhigang Gong <zhigang.gong@intel.com> Date: Fri Feb 27 15:52:59 2015 +0800 Build: use -Bsymbolic to fix conflicts with other LLVM users. As there may be some other LLVM users such as mesa, and they may link to different LLVM library. To avoid such type of conflicts, we use -Bsymbolic to disable the symbol preemption. This patch should fix the build bug at: https://bugs.freedesktop.org/show_bug.cgi?id=89325 Signed-off-by: Zhigang Gong <zhigang.gong@intel.com> diff --git a/CMakeLists.txt b/CMakeLists.txt index b731973..88ff872 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -86,7 +86,7 @@ ELSE (USE_STANDALONE_GBE_COMPILER STREQUAL "true") ENDIF (USE_STANDALONE_GBE_COMPILER STREQUAL "true") -set (CMAKE_SHARED_LINKER_FLAGS "-Wl,--no-undefined ${LLVM_LDFLAGS}") +set (CMAKE_SHARED_LINKER_FLAGS "${CMAKE_SHARED_LINKER_FLAGS} -Wl,-Bsymbolic -Wl,--no-undefined ${LLVM_LDFLAGS}") # XLib Find_Package(X11) Thank you very much for the fast response. You were quite right - that patch has fixed the OpenCL compilation issue but there is a crash when it runs. Unfortunately, I don't have much to give you for debugging it! The following is the output I see on the command line when I try to render the default blender scene (just a cube) using the Cycles Renderer : [arpie@max build]$ CYCLES_OPENCL_TEST=true blender Read new prefs: /home/arpie/.config/blender/2.73/config/userpref.blend Device init succes Compiling OpenCL kernel ... %132 = load i32 addrspace(2)* %131, align 4, !tbaa !54 Illegal pointer which is not from a valid memory space. Aborting... Should I report this as a new bug? Is there any way I can get more verbose output to help track it down? Equally, do you think it is too ambitious to be trying to get this to work at all? I suspect the speed up I will get will be minimal (if any at all), as I am not exactly using a high-spec GPU. In fact, that might be the cause of the crash - not enough memory available on the GPU? But that is just a naive guess! I should stop speculating and leave it to the experts... Russell (In reply to Russell Palmer from comment #2) > Thank you very much for the fast response. You were quite right - that > patch has fixed the OpenCL compilation issue but there is a crash when it > runs. Unfortunately, I don't have much to give you for debugging it! The > following is the output I see on the command line when I try to render the > default blender scene (just a cube) using the Cycles Renderer : > > [arpie@max build]$ CYCLES_OPENCL_TEST=true blender > Read new prefs: /home/arpie/.config/blender/2.73/config/userpref.blend > Device init succes > Compiling OpenCL kernel ... > %132 = load i32 addrspace(2)* %131, align 4, !tbaa !54 > Illegal pointer which is not from a valid memory space. > Aborting... I can't reproduce this. Could you tell me the LLVM/Clang version you are using? You can get it by execute: llvm-config --version. > > > Should I report this as a new bug? It's better to file new bug for a different symptom. So I change the subject of this bug report to accurate indicate the original issue you met. > > Is there any way I can get more verbose output to help track it down? > > Equally, do you think it is too ambitious to be trying to get this to work > at all? I suspect the speed up I will get will be minimal (if any at all), > as I am not exactly using a high-spec GPU. In fact, that might be the cause > of the crash - not enough memory available on the GPU? But that is just a > naive guess! I should stop speculating and leave it to the experts... To support blender's CYCLE engine is a little bit ambitious due to its very large computing kernel. But we will continue to improve beignet to support it eventually. Don't know which GPU are you using, if you are using a HSW GT3, then if we can get blender work with beignet, it should give noticeable performance boost. If you are using IVB GT1 or HSW GT1, then it may not worth to enable GPU acceleration. > > Russell |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.