similar to: [LLVMdev] likely SPECCPU2006 miscompilation

Hi If so, is it able to disable this check. All I need is just to get the BB coverage information Regards Muhui Alexander Potapenko <glider at google.com>于2018年9月5日 周三下午6:57写道： > This is a known problem in SPECCPU2006, see > https://github.com/google/sanitizers/wiki/AddressSanitizerFoundBugs > On Wed, Sep 5, 2018 at 7:36 AM Muhui Jiang via llvm-dev > <llvm-dev at

Hi Alex Thanks for your email. But it seems not work. I removed the -fsanitize=address flag. The global buffer overflow message doesn't show. However, no *.sancov file is created after I run perlbench. Thus, I could not get the BB coverage. Do you have any ideas? Many Thanks Regards Muhui Alexander Potapenko <glider at google.com> 于2018年9月5日周三 下午7:14写道： > Hi Muhui, > > If

Filed a bug with Apple 10073924  but I'm wondering if anyone else knows what to fix here: Summary: Building a Darwin cross compiler so I can use distcc with my Mac. Host: x86_64-gnu-linux with GCC 4.5.3. Steps to Reproduce: Download tar ball tar xvf llvmgcc42-2335.15.tar.gz mkdir gcc-build cd gcc-build CFLAGS="-w -m32" CXXFLAGS="$CFLAGS" CPPFLAGS="$CFLAGS"

Hi I am using SanitizerCoverage feature supported by clang to get the basicblock coverage. my tested binaries are spec cpu2006. I compiled the binary with the option COPTIMIZE = -O0 -fsanitize=address -fsanitize-coverage=bb -flto -fno-strict-aliasing -std=gnu89 -gdwarf-3 After the compiling process is end. I run the 400.perlbench. with the command ASAN_OPTIONS=coverage=1 ./perlbench.

On 11 March 2013 16:13, Anitha B Gollamudi <anitha.boyapati at gmail.com> wrote: > On 11 March 2013 10:06, Anitha B Gollamudi <anitha.boyapati at gmail.com> wrote: >> On 23 January 2013 00:20, Craig Topper <craig.topper at gmail.com> wrote: >>> >>> Are you still having issues with FMA4? I wonder if PR15040 is related. A >>> fix was just

Hello, I'm trying to generate bitcode files from the SPEC CPU2006 benchmark suites. First I installed the benchmarks into ~/llvm/projects/test-suite/External/speccpu2006 and then I tried ~/mysandbox/bin/lnt runtest nt --sandbox=sandbox --cc=/Users/asd/llvm/Release/bin/clang --test-suite=/Users/asd/llvm/projects/test-suite --test-externals=/Users/asd/llvm/projects/test-suite/External -j 4

>> Dear All, I have been trying for days but still cannot break this barrier. May I get your help? I have compiled llvm-2.1 successfully and make install. When I proceed with llvm-gcc-4.2-2.1, however, I keep getting linking error as attached. Some functions with totally different content conflict with each other in linking process. That is a Linux box (Debian, with 2.6.23-1

Hi, I am getting this when running make-test :- $ /usr/src/llvm-test-2.5/configure checking for spec95 benchmark sources... no, not found in /home/vadve/shared/ben chmarks/spec95/benchspec checking for spec2000 benchmark sources... no, not found in /home/vadve/shared/b enchmarks/speccpu2000/benchspec checking for spec2006 benchmark sources... no, not found in /home/vadve/shared/b

These benchmarks are not distributed with llvm (which doesn't have the legal right to distribute Spec, for example). If you have them from another source, you need to configure --with-externals=<path> On Feb 23, 2009, at 10:02 AMPST, Aaron Gray wrote: > Hi, > > I am getting this when running make-test :- > > $ /usr/src/llvm-test-2.5/configure > checking for

Hello, I'd like to propose the addition of a new SystemZ backend to the LLVM and Clang code base. We're interested in this for the same reason we've been interested in the PowerPC back-end recently: to enable packages in upcoming enterprise Linux distributions that need LLVM support (e.g. 3D desktop support via llvmpipe). Now, I understand that a SystemZ backend used to be part of

I can't really tell what is happening based on this output, but 'make' is not the right way to build SPECcpu2006 components. You need to do either by using the supplied 'runspec' command with '-build' action directive or to issue the 'specmake' (which is a make adjusted by spec.org) on the build component folder. I can build 433.milc on PPC64 with clang without

On Mon, Feb 23, 2009 at 6:09 PM, Dale Johannesen <dalej at apple.com> wrote: > These benchmarks are not distributed with llvm (which doesn't have the > legal right to distribute Spec, for example). If you have them from > another source, you need to configure --with-externals=<path> Okay, thanks. Thre should be better warning/error reporting though. Aaron > >

On Mon, Feb 23, 2009 at 6:22 PM, Aaron Gray <aaronngray.lists at googlemail.com > wrote: > On Mon, Feb 23, 2009 at 6:09 PM, Dale Johannesen <dalej at apple.com> wrote: > >> These benchmarks are not distributed with llvm (which doesn't have the >> legal right to distribute Spec, for example). If you have them from >> another source, you need to configure

I've noticed that LLVM does a bad job of optimizing array indexing code for FORTRAN arrays declared using the ALLOCATABLE keyword. For example if you have something like the following: DOUBLE PRECISION,ALLOCATABLE,DIMENSION(:,:,:,:) :: QAV ... ALLOCATE( QAV( -2:IMAX+2,-2:JMAX+2,-2:KMAX+2,ND) ) ... DO L = 1, 5 DO K = K1, K2 DO J = J1, J2 DO I = I1, I2 II = I +

Actually I am trying to run SPEC2006 through the Makefiles provided with LLVM Test Suite, so I think it should work properly... On 18 February 2013 15:49, Adhemerval Zanella <azanella at linux.vnet.ibm.com>wrote: > I can't really tell what is happening based on this output, but 'make' is > not the right way > to build SPECcpu2006 components. You need to do either by

Hi Wonsun, can you please provide a testcase. Best wishes, Duncan. > I've noticed that LLVM does a bad job of optimizing array indexing > code for FORTRAN arrays declared using the ALLOCATABLE keyword. > > For example if you have something like the following: > > DOUBLE PRECISION,ALLOCATABLE,DIMENSION(:,:,:,:) :: QAV > ... > ALLOCATE( QAV(

I am trying to build the llvm-gcc frontend. I think I have followed the directions correctly. I am using cygwin on XP SP2 (uname -a reports: CYGWIN_NT-5.1 pad7 1.5.25(0.156/4/2) 2007-12-14 19:21 i686 Cygwin) gcc --version reports: gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) Since there is no binary for llvm-gcc I am following the directions in the tar file for the 4.2 version. -

Hello, all- I am having trouble getting the test suite set up with my download of SPEC2006. I downloaded and installed llvm-gcc, checked out a copy of test-suite in llvm-2.8/projects, and then configured and made llvm: ./configure --enable-debug-runtime --disable-optimized --enable-spec2006=/home/jamiemmt/speccpu2006 --with-externals=/home/jamiemmt make The configure script found the SPEC

It doesn't build. llvm-main.cpp doesn't get compiled for some reason: g++40 -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -fno-common -DHAVE_CONFIG_H -DENABLE_LLVM -D__STDC_LIMIT_MACROS -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/../include -I./../intl

On Feb 23, 2009, at 10:30 AMPST, Aaron Gray wrote: > On Mon, Feb 23, 2009 at 6:22 PM, Aaron Gray <aaronngray.lists at googlemail.com > > wrote: > On Mon, Feb 23, 2009 at 6:09 PM, Dale Johannesen <dalej at apple.com> > wrote: > These benchmarks are not distributed with llvm (which doesn't have the > legal right to distribute Spec, for example). If you have