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

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

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 Thu, 9 Sep 2010 02:19:11 -0700 (PDT) markhor <markhor at ispras.ru> wrote: > > Hello. > > I experience a problem when I try to run LLVM tests on the ARM > "Beagle" board with Debian Lenny installed on it. I got this email 9 times at a difference of a few minutes, did you send it that many times, or something wrong with the mailing list? Best regards, --Edwin

2012/12/30 Larry Evans <cppljevans at suddenlink.net>: > I just created clang with the tarballs without problem; however, > when `make check-all` was run, I got 1 error. My system is: > ~/download/llvm/pre-releases/3.2/rc3/download/build_debug $ make check-all > llvm[0]: Running test suite > make[1]: Entering directory >

On Sun, Dec 30, 2012 at 1:58 AM, Larry Evans <cppljevans at suddenlink.net>wrote: > On 12/29/12 18:40, NAKAMURA Takumi wrote: > > 2012/12/30 Larry Evans <cppljevans at suddenlink.net>: > >> I just created clang with the tarballs without problem; however, > >> when `make check-all` was run, I got 1 error. My system is: > > > >>

Török Edwin <edwintorok at gmail.com> writes: >> > Which regression tests are failing with LLVM 2.8 and GCC 4.4.x? >> >> Too many to list. > > Can you give me 2 or 3 examples (that fail with LLVM 2.8 and GCC 4.4 > but work with LLVM 2.8 and GCC 4.3), also I'd like to know how they > fail. > If I have some time I'll check with my 4.4 to see if

On 12/06/12 01:12, Pawel Wodnicki wrote: > Hello, > > Release Candidate 3 has been branched. > RC3 source code can be downloaded as tarballs from: > > http://llvm.org/pre-releases/3.2/rc3/ > > or directly from svn. > > Binaries will be posted shortly. > > Testing > > RC3 has a number of fixes related to MIPS support > that need to be well

On Wed, Jan 4, 2012 at 12:10 PM, David Gardner <daveg at xmos.com> wrote: > Jianzhou Zhao <jianzhou <at> seas.upenn.edu> writes: >> The documents say that all the aa analysis are chained, and give an >> example like opt -basicaa -ds-aa -licm. In this case, does ds-aa >> automatically call basicaa for the case when ds-aa can only return >> MayAlias? This

Jianzhou Zhao <jianzhou <at> seas.upenn.edu> writes: > At this level, I can understand how it works. I was confused because I > have been looking at the source code for implementing them. All the > globalmodref, scev-aa, steenaa and ds-aa are only subclasses of the > AliasAnalysis class, so I cannot see how ds-aa can automatically call > basicaa. There's some magic

In our case basicaa alone returns "may alias" on our pointers and we want to override that with tbaa data to "Wont alias" when we know that the pointers will never alias. So its not covered by your case. Since the basicaa pass doesnt chain according to the llvm docs, it should have the last chance to affect the aliasing information, and that means it should be added first. If

[+llvmdev] Rajeshwar Vanka wrote: > -----Original Message----- > From: Nick Lewycky [mailto:nicholas at mxc.ca] > Sent: Wednesday, November 24, 2010 3:51 PM > To: dirac > Cc: llvmdev at cs.uiuc.edu > Subject: Re: [LLVMdev] Question regarding the alias analysis chaining > behaviour > > dirac wrote: >> Hi, >> I am using LLVM 2.4 on a Linux RHEL5 machine.

On Thu, Nov 8, 2012 at 6:53 PM, Pranav Bhandarkar <pranavb at codeaurora.org> wrote: > Hi, > > I am observing some incorrect behavior in basicaa, wherein two pointers that > basicaa should determine to be MustAlias are ending up NoAlias - the other > extreme :( > I am blaming this on basicaa not handling inttoptr. Here is the relevant IR > snippet. >

AliasAnalysis and dependence analysis answer different problems. AA check whether two memory ranges accessed at the same time (i.e. in the same iteration) do not overlap. DI checks when two accesses, not necessarily executed in the same iteration, do overlap. DI makes use of AA in verifying that the base pointer (with unknown size), at the beginning of the loop, themselves do not overlap. If they