----- 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
İsmail, I just completed a stage2 build r204801, compiled with: make -j 32 ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1 OPTIMIZE_OPTION='-O3 -mcpu=native' and I don't see this problem. This was on a P7 box. -Hal ----- Original Message -----> From: "Hal Finkel" <hfinkel at anl.gov> > To: "Renato Golin" <renato.golin at linaro.org>, "Will Schmidt" <will_schmidt at vnet.ibm.com> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > Sent: Wednesday, March 26, 2014 8:28:02 AM > Subject: Re: [LLVMdev] Lots of regtest failures on PPC64/Linux > > ----- 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 > > _______________________________________________ > 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
Hi Hal, On Wed, Mar 26, 2014 at 3:42 PM, Hal Finkel <hfinkel at anl.gov> wrote:> İsmail, > > I just completed a stage2 build r204801, compiled with: > > make -j 32 ENABLE_OPTIMIZED=1 DISABLE_ASSERTIONS=1 OPTIMIZE_OPTION='-O3 > -mcpu=native' > > and I don't see this problem. This was on a P7 box. >I will try with -mcpu=native but note that I use cmake hence things can be very different compared to autoconf (all shared libs. case). Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140326/0d80da8c/attachment.html>
On Wed, 2014-03-26 at 08:28 -0500, Hal Finkel wrote:> ----- 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? > > -Halthe mcpu=native bot is this one: {'name' : "clang-ppc64-elf-linux", 'slavenames' :["chinook-clangslave1"], ... There is no stage*_config= value specified. A glance at the builder itself shows "Release+Asserts". note: that bot is continuing to fail during the LNT test with errors such: " main.py:147: warning: --commit should be passed directly to the test suite. ... lnt: error: no such option: -m " i.e. http://lab.llvm.org:8011/builders/clang-ppc64-elf-linux/builds/7269/steps/lnt.nightly-test/logs/stdio> > > 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 > > >