similar to: [LLVMdev] How to run regression tests for ARM?

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory `/mnt/markhor/llvm/nativeBuild/test' Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory `/mnt/markhor/llvm/nativeBuild/test' Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory `/mnt/markhor/llvm/nativeBuild/test' Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: || llvm[0]: Running test suite make[1]: Entering directory `/mnt/markhor/llvm/nativeBuild/test' Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory `/mnt/markhor/llvm/nativeBuild/test' Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory `/mnt/markhor/llvm/nativeBuild/test' Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory /mnt/markhor/llvm/nativeBuild/test Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000 ; \

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory `/mnt/markhor/llvm/nativeBuild/test' Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000

Hello. I experience a problem when I try to run LLVM tests on the ARM "Beagle" board with Debian Lenny installed on it. When I execute "make check", I get the following output: llvm[0]: Running test suite make[1]: Entering directory /mnt/markhor/llvm/nativeBuild/test Making a new site.exp file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 512000 ; \

On Tue, Jan 3, 2012 at 4:55 PM, Chris Lattner <clattner at apple.com> wrote: > On Jan 3, 2012, at 1:53 PM, Jianzhou Zhao wrote: >> I see. I asked the question because LLVM provides several alias >> analysis, and I was wondering how to decide which one should be used >> for compiling most programs. >> >> I think the basicaa is the default one, but by looking

On Jan 3, 2012, at 1:53 PM, Jianzhou Zhao wrote: > I see. I asked the question because LLVM provides several alias > analysis, and I was wondering how to decide which one should be used > for compiling most programs. > > I think the basicaa is the default one, but by looking into its code, > it is not inter-procedural or context-sensitive (I am not 100% sure), > so does not

<div>Need help about Alias Analysis.</div><div>I try to detect use-after-free debug in source code. And my analysis is based on LLVM IR.</div><div>I use the following code as a small example. I want to get the result p&&q are alias.</div><div>//uaf.cpp</div><div><div>#include<iostream></div><div>using namespace

Hi Xin, Thank you for your reply! I have tried the 3 alias analyses you have mentioned on LLVM 3.5: 1) $ opt -globalsmodref-aa -aa-eval < xxx.bc > /dev/null (May-alias response 100%) 2) $ opt -tbaa -aa-eval < xxx.bc > /dev/null (May-alias response 100%) 3) $ opt -cfl-aa -aa-eval < xxx.bc> /dev/null (Unknown command line argument '-cfl-aa') It seems that they are not

Can you say what Benchmark or give a test case so we understand the nature of the regression? As Gerolf said, that will be important to understand what is best to do. On Fri, Jul 17, 2015, 06:43 Evgeny Astigeevich <Evgeny.Astigeevich at arm.com> wrote: > Yes, the regression is stable. I double checked this. A full benchmark > run consists of at least 10 sub-runs to validate the

Before the fix, the compiler may simply return 'noalias' for cases it can not really prove to be noalias, but actually correct by luck (or even wrong noalias, but does not result in miscompile). It would be useful to find out the set of missed noalias queries from GlobalModRef with your benchmark and examine if there is some improvement can be done. David On Fri, Jul 17, 2015 at 6:32

Hi I have this program in which fooBuf can only take on NULL or the address of local_fooBuf, and fooBuf and local_fooBuf have scope of the foo function. Therefore there is no way for the fooPtr argument to alias with fooBuf. However, LLVM basicaa and globalsmodref-aa say the 2 pointers may alias. I am thinking whether i should implement a limited form of point-to alias on the fooBuf pointer in

On Wed, 2007-03-21 at 13:29 -0700, Wei Jiang wrote: > hi, > The llvm alias analysis doc mentioned that llvm have various alias > analysis passes, e.g. steens-aa; but I can't find it in llvm 2.0. Are > these passes obsoleted? Thanks. I think that Steensgaard was part of the data structure analysis which has been moved out of llvm. We currently have -basicaa, -globalsmodref-aa,

Hi Chandler, I would like to run some benchmarks on ARM hardware and to look at impact of your patches on LTO. Kind regards, Evgeny Astigeevich From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Chandler Carruth Sent: 15 July 2015 10:45 To: Chandler Carruth; Gerolf Hoflehner Cc: LLVM Developers Mailing List Subject: Re: [LLVMdev] GlobalsModRef

Hi Alexandre, The script uses extended-sed syntax, so you need to run sed with the -E option. For example, when preparing the patch I created a file ( script.sed ) containing all of the lines that I copied into the commit message. Then, I ran this bash one-liner from the test directory: for f in $(find . -name '*.ll'); do sed -E -i ‘.sedbak' -f script.sed $f; done When I was happy

Hi there, I am doing: opt -print-memdeps ./test.bc -analyze -globalsmodref-aa by adding globalsmodref-aa, I am hoping that globalsmodref alias analysis will be used. However, it does not turn out to be so. I found this out by adding some "errs() << " into the source code for that alias analysis. So my question is what should I do to let memory dependency analysis use