similar to: [LLVMdev] Unexpected failures in the DejaGNU test collection

On 14/07/2009, at 12.35, Harel Cain wrote: > When using "make check" with the DejaGNU test collection, I encounter > two unexpected failures (they seem to be closely related). > My question: are they well known, and if so what's the problem and how > can I fix it? > FAIL: /var/data/common/trunk/llvm/test/FrontendC/2008-05-19- > AlwaysInline.c > FAIL:

Since it came up, what is blocking us from putting these tests in the llvm-gcc test suite instead of in the LLVM test suite? - Daniel On Tue, Jul 14, 2009 at 4:01 AM, Jakob Stoklund Olesen<stoklund at 2pi.dk> wrote: > > On 14/07/2009, at 12.35, Harel Cain wrote: >> When using "make check" with the DejaGNU test collection, I encounter >> two unexpected failures

Two failing tests on x86-32 linux: FAIL: test/FrontendC/2008-08-07-AlignPadding1.c Failed with exit(1) at line 1 while running: /usr/local/bin/llvm-gcc -emit-llvm -w test/FrontendC/2008-08-07-AlignPadding1.c -m64 -S -o - -emit-llvm -O0 | grep

Hi all, while writing a testcase thate needed to do a grep containg {, I found that the DejaGNU test framework didn't handle those very well. It's a bit of a fuss to escape accolades properly, but most of all the framework seemed to silently ignore errors in the escaping (and just not run the command then). See [1]. Fixing the framework resulted in 80 of the tests failing. I spent the

Building r80796 of the "release_26" branch on Ubuntu 9.04, I'm getting an XPASS on: ssen at ssen:~/llvm/build$ make TESTONE=FrontendC/2009-08-11- AsmBlocksComplexJumpTarget.c check-one make[1]: Entering directory `/home/ssen/llvm/build/test' Making a new site.exp file... XPASS: /home/ssen/llvm/test/FrontendC/2009-08-11- AsmBlocksComplexJumpTarget.c make[1]: Leaving directory

I successfully built LLVM (r102824) with ./configure --enable-optimized --enable-targets=host --with-built-clang on Fedora 12 on an Athlon64 processor. (The clang is the 2.7 pre-built version.) However, running `make check' produced 6 unexpected failures (see below). If there's something you'd like me to do, just holler. --- Vladimir FAIL:

On Feb 24, 2011, at 11:36 AM, Devang Patel wrote: > > On Feb 12, 2011, at 2:07 AM, Nathan Jeffords wrote: > >> Hello All, >> >> I have created a set of patches that get dwarf debugging support working for the COFF object file. I also believe I have fixed what appears to be a bug in how line info sections are referred to from the DW_TAG_compile_unit DIE. I have run

I experienced FAIL: /localtmp/astifter/llvm/llvm-svn/test/FrontendC/2007-03-27-VarLengthArray.c Failed with exit(1) at line 1 while running: /nfs/a5/astifter/astifter/llvm/llvm-svn-obj/../llvm-svn-install/bin/llvm-gcc -emit-llvm -w -S /localtmp/astifter/llvm/l lvm-svn/test/FrontendC/2007-03-27-VarLengthArray.c -o - | /bin/grep {getelementptr inbounds \[0 x i32\]} child process exited abnormally

On May 3, 2010, at 10:43 AMPDT, Vladimir G. Ivanovic wrote: > I successfully built LLVM (r102824) with > > ./configure --enable-optimized --enable-targets=host --with-built-clang > > on Fedora 12 on an Athlon64 processor. (The clang is the 2.7 pre-built > version.) and the llvm-gcc appears to be also? > However, running `make check' produced 6 unexpected failures

on 05/03/2010 11:13 AM Dale Johannesen said the following: > On May 3, 2010, at 10:43 AMPDT, Vladimir G. Ivanovic wrote: > > >> I successfully built LLVM (r102824) with >> >> ./configure --enable-optimized --enable-targets=host --with-built-clang >> >> on Fedora 12 on an Athlon64 processor. (The clang is the 2.7 pre-built >> version.) > > and

on 05/03/2010 12:43 PM Dale Johannesen said the following: > However, running `make check' produced 6 unexpected failures >>>> (see below). If there's something you'd like me to do, just holler. >>> >>> In general, tests added after a branch forked won't pass on that branch. That accounts for these at least: >> I don't understand. These

Hi all, I recently experienced the same issue as below with LLVM 2.8 on Mac OS 10.5.8. I can load the pass with the debug version of opt, but not the optimized version. Does anyone know what the problem is or have any suggestions for debugging this? My install went fine except for some failures during make check (Unexpected Failures: 92). All failures were in one of the following:

Hi, There is a problem with the handling of alwaysinline functions in Clang: they are not always inlined. AFAIK, this may only happen when the caller is in the dead code, but then we don't always successfully remove all dead code. Because of this, we may end up emitting an undefined reference for an "inline __attribute__((always_inline))" function. Libc++ relies on the compiler

Hello all, I have a custom allocator, and would like to teach LLVM about its semantics. In particular, I would like LLVM to kill allocations that are "dead", similar to dead new in C++. Consider this example: ; ModuleID = '<stdin>' source_filename = "Module" ; Function Attrs: inaccessiblememonly noinline norecurse nounwind declare i8* @alloc(i64)

On Thu, Aug 20, 2015 at 7:17 PM, John McCall <rjmccall at apple.com> wrote: > > On Aug 20, 2015, at 5:19 PM, Evgenii Stepanov via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > > Hi, > > > > There is a problem with the handling of alwaysinline functions in > > Clang: they are not always inlined. AFAIK, this may only happen when > > the caller is

Hi Duncan, thanks for the quick answer. Yes I'm sure the runOnModule is being called, and when I dump the functions before exiting the method I can see the AlwaysInline attribute. I'll check InlineAlways.cpp and will reimplement as last resource but I still wonder why this is not working. On Mon, Nov 5, 2012 at 5:03 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi Arnaldo,

On 01/08/2010 02:10 PM, John McCall wrote: > 'llc' is an IR-to-assembly compiler; at -O3 it does some pretty neat > machine-code and object-file optimizations, but it does not apply > high-level optimizations like CSE or inlining. 'opt' is the tool > which does IR-to-IR optimization. A vital clue, but I'm still not getting it: --- gemini:~/Projects/Nil/nil(0)$

Hi Arnaldo, On 05/11/12 10:02, Arnaldo wrote: > Hi Duncan, thanks for the quick answer. > > Yes I'm sure the runOnModule is being called, and when I dump the functions > before exiting the method I can see the AlwaysInline attribute. > > I'll check InlineAlways.cpp and will reimplement as last resource but I still > wonder why this is not working. if you want more

On May 3, 2010, at 12:09 PMPDT, Vladimir G. Ivanovic wrote: > on 05/03/2010 11:13 AM Dale Johannesen said the following: >> On May 3, 2010, at 10:43 AMPDT, Vladimir G. Ivanovic wrote: >> >> >>> I successfully built LLVM (r102824) with >>> >>> ./configure --enable-optimized --enable-targets=host --with-built-clang >>> >>> on

On Dec 2, 2010, at 2:37 PM, Scott Ricketts wrote: > My install went fine except for some failures during make check > (Unexpected Failures: 92). All failures were in one of the following: > > LLVM::FrontendC++ > LLVM::FrontendC > LLVM::FrontendObjC++ > LLVM::FrontendObjC These are actually testing llvm-gcc, not llvm. If you build and install llvm-gcc, and tell llvm where