https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c1 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED AssignedTo|bnc-team-xorg-bugs@forge.pr |xorg-maintainer-bugs@forge. |ovo.novell.com |provo.novell.com --- Comment #1 from Stefan Dirsch 2012-02-16 11:44:35 UTC ---

Are you aware of such problems and perhaps a fix?

2x no. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c3 --- Comment #3 from Marcus Meissner 2012-02-16 12:55:24 UTC --- relevant is perhaps also that we do 32bit code on 64bit... so installing glxgears 32bit and trying might trigger this better than glxgears 64bit. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c5 --- Comment #5 from Rafał Miłecki 2012-02-24 16:37:20 UTC --- Note: I'm using 32bit openSUSE, so it's not about 32bit vs. 64bit conflict. I wanted to compile Mesa on my own and I've hit following problem. Maybe there is something wrong with the llvm provided in openSUSE 12.1? g++ -g -O2 -Wall -std=c99 -Werror=implicit-function-declaration -Werror=missing-prototypes -fno-strict-aliasing -fno-builtin-memcmp -g -O2 -fPIC -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -D_GNU_SOURCE -DPTHREADS -DHAVE_POSIX_MEMALIGN -DUSE_XCB -DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DHAVE_ALIAS -DHAVE_MINCORE -DHAVE_LIBUDEV -DHAVE_XCB_DRI2 -DXCB_DRI2_CONNECT_DEVICE_NAME_BROKEN -D__STDC_CONSTANT_MACROS -DHAVE_LLVM=0x0300 -fvisibility=hidden -o r600_dri.so.test ./../../../src/mesa/drivers/dri/common/dri_test.o r600_dri.so.tmp -L../../../../lib -Wl,-R/usr/lib/dri -ldricore -lglsl -ldrm -lexpat -lm -lpthread -ldl -ldrm_radeon -L/usr/lib -ldl -lpthread; r600_dri.so.tmp: undefined reference to `llvm::MCAsmBackend::MCAsmBackend()' r600_dri.so.tmp: undefined reference to `LLVMStructCreateNamed' r600_dri.so.tmp: undefined reference to `llvm::createELFStreamer(llvm::MCContext&, llvm::MCAsmBackend&, llvm::raw_ostream&, llvm::MCCodeEmitter*, bool, bool)' r600_dri.so.tmp: undefined reference to `llvm::MCAsmBackend::getFixupKindInfo(llvm::MCFixupKind) const' r600_dri.so.tmp: undefined reference to `vtable for llvm::MCInstrAnalysis' r600_dri.so.tmp: undefined reference to `llvm::createWinCOFFStreamer(llvm::MCContext&, llvm::MCAsmBackend&, llvm::MCCodeEmitter&, llvm::raw_ostream&, bool)' r600_dri.so.tmp: undefined reference to `llvm::StackAlignmentOverride' r600_dri.so.tmp: undefined reference to `llvm::MCSubtargetInfo::InitMCSubtargetInfo(llvm::StringRef, llvm::StringRef, llvm::StringRef, llvm::SubtargetFeatureKV const*, llvm::SubtargetFeatureKV const*, llvm::SubtargetInfoKV const*, llvm::InstrStage const*, unsigned int const*, unsigned int const*, unsigned int, unsigned int)' r600_dri.so.tmp: undefined reference to `llvm::MCCodeGenInfo::InitMCCodeGenInfo(llvm::Reloc::Model, llvm::CodeModel::Model)' r600_dri.so.tmp: undefined reference to `LLVMStructSetBody' r600_dri.so.tmp: undefined reference to `llvm::X86ATTInstPrinter::X86ATTInstPrinter(llvm::MCAsmInfo const&)' r600_dri.so.tmp: undefined reference to `llvm::MCAsmBackend::~MCAsmBackend()' r600_dri.so.tmp: undefined reference to `llvm::createMachOStreamer(llvm::MCContext&, llvm::MCAsmBackend&, llvm::raw_ostream&, llvm::MCCodeEmitter*, bool)' collect2: ld returned 1 exit status AFAICS in Marcus's bug report, his crash is llvm related! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c7 --- Comment #7 from Rafał Miłecki 2012-02-26 11:09:57 UTC --- I've decided to downgrade llvm. I've downloaded sources of version 2.8 (instead of 3.0) and compiled and installed it. I think everything went fine, now I get:

llvm-config --version 2.8

and mesa's config displays: llvm: yes llvm-config: /usr/bin/llvm-config llvm-version: 2.8 After downgrading llvm, I've recompiled Mesa (same version and same config as earlier). I installed it and wine started to work! I can finally play Diablo II without DRAW_USE_LLVM=0. I guess we should bisect llvm, unfortunately this project doesn't use git (no "git bisect") and recompiling whole llvm and mesa can take a lot of time. But at least we have something to start with. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c9 --- Comment #9 from Rafał Miłecki 2012-02-26 12:06:03 UTC --- (In reply to comment #8)

mesa uses llvm on buildtime, just swapping llvm out in the system is not going to work ... So you need to rebuild Mesa.

So Rafal, you got the 12.1 Mesa compiled with LLVM 2.8? and this helped?

Yes, I'm recompiling whole mesa: make clean; make distclean; make realclean /autogen.sh --prefix=/usr --with-gallium-drivers=r600 --with-dri-drivers= make -j 4 sudo make install every time I change (upgrade/downgrade) llvm. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c11 --- Comment #11 from Rafał Miłecki 2012-02-28 09:05:24 UTC --- Do you have the bug with Mesa 8.0.1 ?(In reply to comment #10)

Do you have the bug with Mesa 8.0.1 ?

Please take a look at comment #6 - I'm using Mesa git. I'm quite sure git master contains every patch that landed in 8.0.1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c13 --- Comment #13 from Marcus Meissner 2012-02-28 23:07:18 UTC --- @vincent: if you have unrelated problems, PLEASE open new bugreports. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c15 --- Comment #15 from Rafał Miłecki 2012-02-29 06:05:29 UTC --- vincent: as I said, the workaround is to: 1) Install LLVM 2.9 stable (because 3.0 contains bug/issue) 2) Recompile Mesa on your own I don't really recommend doing that as you can break your system consistency. I suggest you waiting few days, I hopefully will find the breaking commit and we will be able to really fix this issue (with the help of LLVM/Mesa team). I've spent last day compiling LLVM from git looking for a single bad commit. Without a success. Then I realized compiling from git/svn doesn't set "--enable-optimized" by default. Today I'm testing git commits again, right now I've 11'000 revisions left to bisect. It's a little problematic as API changed many times between 2.9 and 3.0 and sometimes I've to fix Mesa build on my own. But hopefully today/tomorrow I'll finish the process. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c17 --- Comment #17 from Rafał Miłecki 2012-03-01 16:26:16 UTC --- (In reply to comment #16)

I rebuilt LLVM removing stage 2 and stage 3 steps, and the bug disappears With stage 2 however, the crash still occurs.

Apparently this is a bug inside clang (stage 1 build llvm using gcc, stage 2 build llvm using newly compiled clang).

Nice, I didn't have any idea about "stages" in LLVM. I was just bisecting whole LLVM builds. This led me to the first bad commit: commit 42634836e999dfcb59f1f5ea50dfd33442be4b9a Author: Eric Christopher Date: Fri Sep 16 20:36:16 2011 +0000 Have the llvm configure process look for clang, then llvm-gcc, and then gcc on all platforms. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@139934 91177308-0d34-0410-b5e6-96231b3b80d8 I believe it matches what you say. It's some clang related issue. Let's see what Mesa and LLVM guys will say. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c19 --- Comment #19 from Rafał Miłecki 2012-03-01 19:17:43 UTC --- LLVM 2.8 with 42634836e999dfcb59f1f5ea50dfd33442be4b9a cherry-picked didn't compile for me: llvm[3]: Building X86.td assembly matcher with tblgen 0 tblgen 0x081b9d3b Stack dump: 0. Program arguments: /home/zajec/x/llvm-2.8/Release/bin/tblgen -I /home/zajec/x/llvm-2.8/lib/Target/X86 -I /home/zajec/x/llvm-2.8/include -I /home/zajec/x/llvm-2.8/include -I /home/zajec/x/llvm-2.8/lib/Target -gen-asm-matcher -o /home/zajec/x/llvm-2.8/lib/Target/X86/Release/X86GenAsmMatcher.inc.tmp X86.td make[3]: *** [/home/zajec/x/llvm-2.8/lib/Target/X86/Release/X86GenAsmMatcher.inc.tmp] Segmentation fault LLVM 2.9 with 42634836e999dfcb59f1f5ea50dfd33442be4b9a compiled without any problems, however Mesa compiled with that LLVM still crashes. So this bug was present already in 2.9, 42634836e999dfcb59f1f5ea50dfd33442be4b9a commit just exposed it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c Johannes Obermayr changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johannesobermayr@gmx.de See Also| |http://bugs.winehq.org/show | |_bug.cgi?id=30052, | |https://bugs.freedesktop.or | |g/show_bug.cgi?id=41791, | |https://bugs.freedesktop.or | |g/show_bug.cgi?id=44466, | |http://llvm.org/bugs/show_b | |ug.cgi?id=12151 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c22 Ronny Peine changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ronnypeine@gmx.de --- Comment #22 from Ronny Peine 2012-08-18 08:51:46 UTC --- (In reply to comment #21)

we released a llvm 3.0 and Mesa update for 12.1

can anybody check if it is still a problem?

Hi, the bug is still present on openSUSE 12.1. Tested with various 3D applications. Versions: Mesa-7.11-11.4.2 llvm-3.0-1.8.1 Kind regards. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=747333 https://bugzilla.novell.com/show_bug.cgi?id=747333#c24 Johannes Obermayr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |UPSTREAM --- Comment #24 from Johannes Obermayr 2012-10-31 18:43:56 UTC --- Fixed upstream. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.