Hi, Recent trunk has a lot of failures on PPC64/Linux. One seems to be crash with a backtrace like: [ 3149s] -- [ 3149s] 0 libLLVMSupport.so 0x00003fff7ed0b864 llvm::sys::PrintStackTrace(_IO_FILE*) + 4294746876 [ 3149s] 1 libLLVMSupport.so 0x00003fff7ed0bb1c [ 3149s] 2 libLLVMSupport.so 0x00003fff7ed0c520 [ 3149s] 3 linux-vdso64.so.1 0x00003fff7f7b0478 __kernel_sigtramp_rt64 + 0 [ 3149s] 4 libLLVMSupport.so 0x00003fff7ecfb448 llvm::sys::AtomicIncrement(unsigned int volatile*) + 4294685040 [ 3149s] 5 libLLVMCodeGen.so 0x00003fff7f64603c [ 3149s] 6 libLLVMCodeGen.so 0x00003fff7f641f84 [ 3149s] 7 libLLVMCodeGen.so 0x00003fff7f63f16c [ 3149s] 8 libLLVMCodeGen.so 0x00003fff7f5b8220 llvm::MachineFunctionPass::runOnFunction(llvm::Function&) + 4293027568 [ 3149s] 9 libLLVMCore.so 0x00003fff7f35be3c llvm::FPPassManager::runOnFunction(llvm::Function&) + 4294119036 [ 3149s] 10 libLLVMCore.so 0x00003fff7f35c210 llvm::FPPassManager::runOnModule(llvm::Module&) + 4294119968 [ 3149s] 11 libLLVMCore.so 0x00003fff7f35c9d8 llvm::legacy::PassManagerImpl::run(llvm::Module&) + 4294121888 [ 3149s] 12 libLLVMCore.so 0x00003fff7f35d120 llvm::legacy::PassManager::run(llvm::Module&) + 4294123632 [ 3149s] 13 libLLVMMCJIT.so 0x00003fff7eff6a20 llvm::MCJIT::emitObject(llvm::Module*) + 4294875216 [ 3149s] 14 libLLVMMCJIT.so 0x00003fff7eff6dfc llvm::MCJIT::generateCodeForModule(llvm::Module*) + 4294876180 [ 3149s] 15 libLLVMMCJIT.so 0x00003fff7eff7674 llvm::MCJIT::finalizeObject() + 4294878228 [ 3149s] 16 lli 0x000000001000cf9c main + 4294831444 [ 3149s] 17 libc.so.6 0x00003fff7e5f796c [ 3149s] 18 libc.so.6 0x00003fff7e5f7b74 __libc_start_main + 4293370644 Others seems to be unexpected outputs. Any help tracking these down would be appreciated. Thanks, ismail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140326/d044a553/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: ppc64.log.gz Type: application/x-gzip Size: 18878 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140326/d044a553/attachment.bin>
Hi Ismail, Is there a buildbot for that? If not, can you bissect to find the offending commit? cheers, --renato On 26 March 2014 13:04, İsmail Dönmez <ismail at donmez.ws> wrote:> Hi, > > Recent trunk has a lot of failures on PPC64/Linux. One seems to be crash > with a backtrace like: > > [ 3149s] -- > [ 3149s] 0 libLLVMSupport.so 0x00003fff7ed0b864 > llvm::sys::PrintStackTrace(_IO_FILE*) + 4294746876 > [ 3149s] 1 libLLVMSupport.so 0x00003fff7ed0bb1c > [ 3149s] 2 libLLVMSupport.so 0x00003fff7ed0c520 > [ 3149s] 3 linux-vdso64.so.1 0x00003fff7f7b0478 __kernel_sigtramp_rt64 + 0 > [ 3149s] 4 libLLVMSupport.so 0x00003fff7ecfb448 > llvm::sys::AtomicIncrement(unsigned int volatile*) + 4294685040 > [ 3149s] 5 libLLVMCodeGen.so 0x00003fff7f64603c > [ 3149s] 6 libLLVMCodeGen.so 0x00003fff7f641f84 > [ 3149s] 7 libLLVMCodeGen.so 0x00003fff7f63f16c > [ 3149s] 8 libLLVMCodeGen.so 0x00003fff7f5b8220 > llvm::MachineFunctionPass::runOnFunction(llvm::Function&) + 4293027568 > [ 3149s] 9 libLLVMCore.so 0x00003fff7f35be3c > llvm::FPPassManager::runOnFunction(llvm::Function&) + 4294119036 > [ 3149s] 10 libLLVMCore.so 0x00003fff7f35c210 > llvm::FPPassManager::runOnModule(llvm::Module&) + 4294119968 > [ 3149s] 11 libLLVMCore.so 0x00003fff7f35c9d8 > llvm::legacy::PassManagerImpl::run(llvm::Module&) + 4294121888 > [ 3149s] 12 libLLVMCore.so 0x00003fff7f35d120 > llvm::legacy::PassManager::run(llvm::Module&) + 4294123632 > [ 3149s] 13 libLLVMMCJIT.so 0x00003fff7eff6a20 > llvm::MCJIT::emitObject(llvm::Module*) + 4294875216 > [ 3149s] 14 libLLVMMCJIT.so 0x00003fff7eff6dfc > llvm::MCJIT::generateCodeForModule(llvm::Module*) + 4294876180 > [ 3149s] 15 libLLVMMCJIT.so 0x00003fff7eff7674 > llvm::MCJIT::finalizeObject() + 4294878228 > [ 3149s] 16 lli 0x000000001000cf9c main + 4294831444 > [ 3149s] 17 libc.so.6 0x00003fff7e5f796c > [ 3149s] 18 libc.so.6 0x00003fff7e5f7b74 __libc_start_main + > 4293370644 > > Others seems to be unexpected outputs. Any help tracking these down would be > appreciated. > > Thanks, > ismail > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
İsmail, These are self-hosted builds? It seems like a lot of crashes in llvm::sys::AtomicIncrement. -Hal ----- Original Message -----> From: "İsmail Dönmez" <ismail at donmez.ws> > To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Cc: "Hal Finkel" <hfinkel at anl.gov> > Sent: Wednesday, March 26, 2014 8:04:04 AM > Subject: Lots of regtest failures on PPC64/Linux > > > Hi, > > > Recent trunk has a lot of failures on PPC64/Linux. One seems to be > crash with a backtrace like: > > > > [ 3149s] -- > [ 3149s] 0 libLLVMSupport.so 0x00003fff7ed0b864 > llvm::sys::PrintStackTrace(_IO_FILE*) + 4294746876 > [ 3149s] 1 libLLVMSupport.so 0x00003fff7ed0bb1c > [ 3149s] 2 libLLVMSupport.so 0x00003fff7ed0c520 > [ 3149s] 3 linux-vdso64.so.1 0x00003fff7f7b0478 > __kernel_sigtramp_rt64 + 0 > [ 3149s] 4 libLLVMSupport.so 0x00003fff7ecfb448 > llvm::sys::AtomicIncrement(unsigned int volatile*) + 4294685040 > [ 3149s] 5 libLLVMCodeGen.so 0x00003fff7f64603c > [ 3149s] 6 libLLVMCodeGen.so 0x00003fff7f641f84 > [ 3149s] 7 libLLVMCodeGen.so 0x00003fff7f63f16c > [ 3149s] 8 libLLVMCodeGen.so 0x00003fff7f5b8220 > llvm::MachineFunctionPass::runOnFunction(llvm::Function&) + > 4293027568 > [ 3149s] 9 libLLVMCore.so 0x00003fff7f35be3c > llvm::FPPassManager::runOnFunction(llvm::Function&) + 4294119036 > [ 3149s] 10 libLLVMCore.so 0x00003fff7f35c210 > llvm::FPPassManager::runOnModule(llvm::Module&) + 4294119968 > [ 3149s] 11 libLLVMCore.so 0x00003fff7f35c9d8 > llvm::legacy::PassManagerImpl::run(llvm::Module&) + 4294121888 > [ 3149s] 12 libLLVMCore.so 0x00003fff7f35d120 > llvm::legacy::PassManager::run(llvm::Module&) + 4294123632 > [ 3149s] 13 libLLVMMCJIT.so 0x00003fff7eff6a20 > llvm::MCJIT::emitObject(llvm::Module*) + 4294875216 > [ 3149s] 14 libLLVMMCJIT.so 0x00003fff7eff6dfc > llvm::MCJIT::generateCodeForModule(llvm::Module*) + 4294876180 > [ 3149s] 15 libLLVMMCJIT.so 0x00003fff7eff7674 > llvm::MCJIT::finalizeObject() + 4294878228 > [ 3149s] 16 lli 0x000000001000cf9c main + 4294831444 > [ 3149s] 17 libc.so.6 0x00003fff7e5f796c > [ 3149s] 18 libc.so.6 0x00003fff7e5f7b74 __libc_start_main + > 4293370644 > > > Others seems to be unexpected outputs. Any help tracking these down > would be appreciated. > > > Thanks, > ismail > >-- Hal Finkel Assistant Computational Scientist Leadership Computing Facility Argonne National Laboratory
Hi, On Wed, Mar 26, 2014 at 3:14 PM, Renato Golin <renato.golin at linaro.org>wrote:> Hi Ismail, > > Is there a buildbot for that? If not, can you bissect to find the > offending commit?Sadly no. There is only my rpm packages on openSUSE Build System ( https://build.opensuse.org/project/show?project=home%3Anamtrac%3Aclang) which I try to commit daily. I can try to bisect but probably Hal has some ideas for which commit it might broke it. So I'll wait for him to reply first since bisecting this is not easy for me. Thanks, ismail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140326/716be955/attachment.html>
Hi Hal, On Wed, Mar 26, 2014 at 3:17 PM, Hal Finkel <hfinkel at anl.gov> wrote:> İsmail, > > These are self-hosted builds? It seems like a lot of crashes in > llvm::sys::AtomicIncrement.Yes. stage1 clang is used in stage2. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140326/57d187a3/attachment.html>
----- Original Message -----> From: "Renato Golin" <renato.golin at linaro.org> > To: "İsmail Dönmez" <ismail at donmez.ws> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Wednesday, March 26, 2014 8:14:18 AM > Subject: Re: [LLVMdev] Lots of regtest failures on PPC64/Linux > > Hi Ismail, > > Is there a buildbot for that?There *should* be. Will, we have a -mcpu=native bot now, right? Does it compile Release or Release+Asserts? -Hal> If not, can you bissect to find the > offending commit? > > cheers, > --renato > > On 26 March 2014 13:04, İsmail Dönmez <ismail at donmez.ws> wrote: > > Hi, > > > > Recent trunk has a lot of failures on PPC64/Linux. One seems to be > > crash > > with a backtrace like: > > > > [ 3149s] -- > > [ 3149s] 0 libLLVMSupport.so 0x00003fff7ed0b864 > > llvm::sys::PrintStackTrace(_IO_FILE*) + 4294746876 > > [ 3149s] 1 libLLVMSupport.so 0x00003fff7ed0bb1c > > [ 3149s] 2 libLLVMSupport.so 0x00003fff7ed0c520 > > [ 3149s] 3 linux-vdso64.so.1 0x00003fff7f7b0478 > > __kernel_sigtramp_rt64 + 0 > > [ 3149s] 4 libLLVMSupport.so 0x00003fff7ecfb448 > > llvm::sys::AtomicIncrement(unsigned int volatile*) + 4294685040 > > [ 3149s] 5 libLLVMCodeGen.so 0x00003fff7f64603c > > [ 3149s] 6 libLLVMCodeGen.so 0x00003fff7f641f84 > > [ 3149s] 7 libLLVMCodeGen.so 0x00003fff7f63f16c > > [ 3149s] 8 libLLVMCodeGen.so 0x00003fff7f5b8220 > > llvm::MachineFunctionPass::runOnFunction(llvm::Function&) + > > 4293027568 > > [ 3149s] 9 libLLVMCore.so 0x00003fff7f35be3c > > llvm::FPPassManager::runOnFunction(llvm::Function&) + 4294119036 > > [ 3149s] 10 libLLVMCore.so 0x00003fff7f35c210 > > llvm::FPPassManager::runOnModule(llvm::Module&) + 4294119968 > > [ 3149s] 11 libLLVMCore.so 0x00003fff7f35c9d8 > > llvm::legacy::PassManagerImpl::run(llvm::Module&) + 4294121888 > > [ 3149s] 12 libLLVMCore.so 0x00003fff7f35d120 > > llvm::legacy::PassManager::run(llvm::Module&) + 4294123632 > > [ 3149s] 13 libLLVMMCJIT.so 0x00003fff7eff6a20 > > llvm::MCJIT::emitObject(llvm::Module*) + 4294875216 > > [ 3149s] 14 libLLVMMCJIT.so 0x00003fff7eff6dfc > > llvm::MCJIT::generateCodeForModule(llvm::Module*) + 4294876180 > > [ 3149s] 15 libLLVMMCJIT.so 0x00003fff7eff7674 > > llvm::MCJIT::finalizeObject() + 4294878228 > > [ 3149s] 16 lli 0x000000001000cf9c main + 4294831444 > > [ 3149s] 17 libc.so.6 0x00003fff7e5f796c > > [ 3149s] 18 libc.so.6 0x00003fff7e5f7b74 __libc_start_main > > + > > 4293370644 > > > > Others seems to be unexpected outputs. Any help tracking these down > > would be > > appreciated. > > > > Thanks, > > ismail > > > > > > _______________________________________________ > > LLVM Developers mailing list > > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-- Hal Finkel Assistant Computational Scientist Leadership Computing Facility Argonne National Laboratory
Krzysztof Parzyszek
2014-Mar-26 16:27 UTC
[LLVMdev] Lots of regtest failures on PPC64/Linux
On 3/26/2014 8:04 AM, İsmail Dönmez wrote:> > Recent trunk has a lot of failures on PPC64/Linux. One seems to be crash > with a backtrace like:Is this with "make check"? I can try it on my G5/FreeBSD box when I get home. -K -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
Hi, On Wed, Mar 26, 2014 at 6:27 PM, Krzysztof Parzyszek < kparzysz at codeaurora.org> wrote:> On 3/26/2014 8:04 AM, İsmail Dönmez wrote: > >> >> Recent trunk has a lot of failures on PPC64/Linux. One seems to be crash >> with a backtrace like: >> > > Is this with "make check"? I can try it on my G5/FreeBSD box when I get > homemake check-all but yes make check would suffice. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140326/69b60c94/attachment.html>