search for: frontendc

...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? This is the error text I get: FAIL: /var/data/common/trunk/llvm/test/FrontendC/2008-05-19-AlwaysInline.c Failed with exit(1) at line 1 while running: /var/data/common/template_wc//install/bin/llvm-gcc -emit-llvm -w /var/data/common/trunk/llvm/test/FrontendC/2008-05-19-AlwaysInline.c -S -fno-unit-at-a-time -emit-llvm -O0 -o - | not /bin/grep sabrina /var/data/common/trunk/llvm...

Hi, I started playing with llvm on Darwin. When I do a "make check" from the llvm root, I am getting these failed tests: Failing Tests (13):     LLVM :: FrontendC++/2010-04-30-OptimizedMethod-Dbg.cpp     LLVM :: FrontendC++/2010-05-12-PtrToMember-Dbg.cpp     LLVM :: FrontendC/2007-05-16-EmptyStruct.c     LLVM :: FrontendC/2007-10-01-BuildArrayRef.c     LLVM :: FrontendC/2010-08-12-asm-aggr-arg.c     LLVM :: FrontendC/2010-11-16-asmblock.c     LLVM :: Fronten...

...ng /home/kooijman/src/llvm-trunk/test/DebugInfo/dg.exp ... Running /home/kooijman/src/llvm-trunk/test/ExecutionEngine/dg.exp ... Running /home/kooijman/src/llvm-trunk/test/Feature/dg.exp ... Running /home/kooijman/src/llvm-trunk/test/FrontendAda/dg.exp ... Running /home/kooijman/src/llvm-trunk/test/FrontendC/dg.exp ... FAIL: /home/kooijman/src/llvm-trunk/test/FrontendC/2002-07-14-MiscTests.c Failed with unknown error (or has stderr output) at line 1 while running: /home/kooijman/src/llvm-gcc/install/bin/llvm-gcc -emit-llvm -S /home/kooijman/src/llvm-trunk/test/FrontendC/2002-07-14-MiscTests.c -o - | l...

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 {zeroinitializer.*zeroinitializer.*zeroinitializer.*zer...

...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: /var/data/common/trunk/llvm/test/FrontendC/always-inline.c Hello Harel, Failures in the FrontendC test suite usually means that your llvm-gcc is older than your LLVM tree. Try compiling llvm-gcc from top-of-tree and see if the failures remain. Regar...

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 `/home/ssen/llvm/build/test' ssen at ssen:~/l...

...es while the >> transition happens. >> >> Ok to commit? > > I'm Ok with this patch. So I'm getting some mysterious failures with this. Currently TOT is failing six tests, which look like this: [x86_64-off-dbg]: FAIL: /ptmp/dag/llvm-project.official/llvm/trunk/test/FrontendC/2010-06-28-DbgLocalVar.c [x86_64-off-dbg]: Failed with exit(1) at line 2 [x86_64-off-dbg]: while running: grep DW_TAG_structure_type 2010-06-28-DbgLocalVar.c.tmp.s | count 2 [x86_64-off-dbg]: Expected 2 lines, got 0. I am getting some additional failures with my patch that look like this: [x86_64...

...d failures (see below). If there's something you'd like me to do, just holler. --- Vladimir FAIL: /usr/local/src/llvm/test/Bindings/Ocaml/vmcore.ml Failed with exit(10) at line 2 while running: ./vmcore.ml.tmp vmcore.ml.tmp.bc FAILED: builder/builder/dbg #1 FAIL: /usr/local/src/llvm/test/FrontendC/crash-invalid-array.c for PR6913 Failed with exit(1) at line 1 while running: not /usr/local/llvm-gcc4.2-2.7-x86_64-linux/bin/llvm-gcc -emit-llvm -w -O1 /usr/local/src/llvm/test/FrontendC/crash-invalid-array.c -S |& /bin/grep {error: invalid use of array with unspecified bounds} child process...

Hi David, On Fri, Jul 9, 2010 at 3:25 PM, David Greene <dag at cray.com> wrote: > Now that Bruno is putting in some AVX stuff, it's a good motivator to > move my x86 SIMD reorg work into trunk (and got management to agree to > prioritize it - Thanks Bruno! :) ). > > Attached is the first patch of many to accomplish this.  The overall > goal is to have all x86 SIMD

Now that Bruno is putting in some AVX stuff, it's a good motivator to move my x86 SIMD reorg work into trunk (and got management to agree to prioritize it - Thanks Bruno! :) ). Attached is the first patch of many to accomplish this. The overall goal is to have all x86 SIMD instructions share a set of common patterns so that we can have a more maintainable machine description (e.g. SS, SD,

...(this is where the bug fix is) >> >> coff-debug.patch >> turns the dwarf output on in the X86/COFF AsmInfo classes > > This patches look fine. I am curious, how are you testing debug info support for COFF ? Well, this patch fails following FE tests on darwin. LLVM :: FrontendC++/2006-11-06-StackTrace.cpp LLVM :: FrontendC++/2006-11-30-Pubnames.cpp LLVM :: FrontendC++/2010-08-31-ByValArg.cpp LLVM :: FrontendC/2009-02-17-BitField-dbg.c LLVM :: FrontendC/2010-01-14-StaticVariable.c LLVM :: FrontendC/2010-02-16-DbgVarScope.c LLVM :: FrontendObjC/2009-...

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\]}...

...gt; 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: > FAIL: /usr/local/src/llvm/test/FrontendC/inline-asm-function.c > Failed with exit(1) at line 1 > while running: /usr/local/llvm-gcc4.2-2.7-x86_64-linux/bin/llvm-gcc > -emit-llvm -w -S > /usr/local/src/llvm/test/FrontendC/inline-asm-function.c -fasm-blocks -o > - -O | /bin/grep naked > child process exited abnormally &g...

...e such (heretofore) unmentioned dependencies that require a post-2.7 version of llvm-gcc to pass? --- Vladimir Vladimir G. Ivanovic http://www.leonora.org +1 650 450 4101 vladimir at acm.org >> FAIL: /usr/local/src/llvm/test/FrontendC/inline-asm-function.c >> Failed with exit(1) at line 1 >> while running: /usr/local/llvm-gcc4.2-2.7-x86_64-linux/bin/llvm-gcc >> -emit-llvm -w -S >> /usr/local/src/llvm/test/FrontendC/inline-asm-function.c -fasm-blocks -o >> - -O | /bin/grep naked >> child proc...

...ing 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 are tests in the LLVM testsuite, not llvm-gcc >> tests. > > Tests in FrontendC and FrontendC++ are tests of llvm-gcc. In general, tests in a particular distribution test that distribution and not some other. -- Vladimir Vladimir G. Ivanovic http://www.leonora.org +1 650 450 4101 vladimir at acm.org > &gt...

...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: LLVM::FrontendC++ LLVM::FrontendC LLVM::FrontendObjC++ LLVM::FrontendObjC LLVM::Transforms Thanks, Scott On Tue, Mar 16, 2010 at 9:24 AM, Ben Ransford <ransford at cs.umass.edu> wrote: > Hello, > > I just built a virgin ToT (r98634) for release on vanilla Snow > Leopard.  It seems that the Hell...

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 some basic tests, analyzed dumps of both the objects files and the final

...t;>> >>> coff-debug.patch >>> turns the dwarf output on in the X86/COFF AsmInfo classes >> >> This patches look fine. I am curious, how are you testing debug info support for COFF ? > > Well, this patch fails following FE tests on darwin. > LLVM :: FrontendC++/2006-11-06-StackTrace.cpp > LLVM :: FrontendC++/2006-11-30-Pubnames.cpp > LLVM :: FrontendC++/2010-08-31-ByValArg.cpp > LLVM :: FrontendC/2009-02-17-BitField-dbg.c > LLVM :: FrontendC/2010-01-14-StaticVariable.c > LLVM :: FrontendC/2010-02-16-DbgVarScope.c > LL...

...ng "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: /var/data/common/trunk/llvm/test/FrontendC/always-inline.c > > Hello Harel, > > Failures in the FrontendC test suite usually means that your llvm-gcc > is older than your LLVM tree. > > Try compiling llvm-gcc from top-of-tree a...

OK , grepping the whole source tree for 'ctlz' I found the answer to my question in: test/FrontendC/2006-01-16-BitCountIntrinsicsUnsigned.c and that is to use gnu frontend style __builtin_clz() for this one. This test/FrontendC directory has a plethora of other usefull examples so I guess It will be sufficient for me. However I still think that some documentation of the frontend interface...