search for: vacopy

Hi, Its that time of the year again. Here is the results on openSUSE 13.1 PPC64. Total of 3 failures which seems to be due the same problem (the value in brackets is the time counter from the build system): [ 3468s] /home/abuild/rpmbuild/BUILD/llvm/test/CodeGen/PowerPC/ppc32-vacopy.ll:21:10: error: expected string not found in input [ 3468s] ; CHECK: lwz [[REG3:[0-9]+]], {{.*}} [ 3468s] ^ [ 3468s] <stdin>:15:2: note: scanning from here [ 3468s] stw 5, 16(1) [ 3468s] ^ [ 3468s] <stdin>:17:3: note: possible intended match here [ 3468s] stw 4, 4(7) [ 3468...

...Here is the results on openSUSE 13.1 > PPC64. > > > Total of 3 failures which seems to be due the same problem (the value > in brackets is the time counter from the build system): > > > > > [ 3468s] > /home/abuild/rpmbuild/BUILD/llvm/test/CodeGen/PowerPC/ppc32-vacopy.ll:21:10: > error: expected string not found in input > [ 3468s] ; CHECK: lwz [[REG3:[0-9]+]], {{.*}} > [ 3468s] ^ > [ 3468s] <stdin>:15:2: note: scanning from here > [ 3468s] stw 5, 16(1) > [ 3468s] ^ > [ 3468s] <stdin>:17:3: note: possible intended match here >...

Hello > What does these mean? The bytecode contains call to intrinsic, which is not supported by by MSIL backend. The only intrinsics currently supported 'natively' are vastart, vaend, vacopy. You might want to extend MSILWriter to use default intrinsic lowering mechanism, however, don't expect, that you'll have something workable - in general, you cannot just grab .c file, translate it with llvm-gcc to .bc and use MSIL writer - you will still need implementations of bunch of...

...sts/2006-02-04-DivRem SingleSource/UnitTests/2006-12-01-float_varg SingleSource/UnitTests/2006-12-04-DynAllocAndRestore SingleSource/UnitTests/2006-12-07-Compare64BitConstant SingleSource/UnitTests/2006-12-11-LoadConstants SingleSource/UnitTests/2007-01-04-KNR-Args SingleSource/UnitTests/2007-03-02-VaCopy SingleSource/UnitTests/2007-04-25-weak SingleSource/UnitTests/2008-04-18-LoopBug SingleSource/UnitTests/2008-04-20-LoopBug2 SingleSource/UnitTests/2008-07-13-InlineSetjmp SingleSource/UnitTests/2009-04-16-BitfieldInitialization SingleSource/UnitTests/2009-12-07-StructReturn SingleSource/UnitTests/2...

...ce/UnitTests/2009-12-07-StructReturn | * | * | SingleSource/UnitTests/2002-12-13-MishaTest | * | * | SingleSource/UnitTests/printargs | * | * | SingleSource/UnitTests/2007-03-02-VaCopy | * | * | SingleSource/UnitTests/2003-08-11-VaListArg | * | * | SingleSource/UnitTests/2003-07-10-SignConversions | * | * | SingleSource/UnitTests/2003-09-18-BitFieldTest...

...* 0.05 | - - n/a n/a SingleSource/UnitTests/2007-01-04-KNR-Args | 0.0037 616 0.0032 * 0.0028 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a SingleSource/UnitTests/2007-03-02-VaCopy | 0.0036 800 0.0034 * 0.0032 | 0.00 0.00 0.00 * 0.00 | - - n/a n/a SingleSource/UnitTests/2007-04-10-BitfieldTest | 0.0018 548 0.0021 * 0.0019...

...* 0.06 | - - n/a n/a SingleSource/UnitTests/2007-01-04-KNR-Args | 0.0040 616 0.0000 * 0.0080 | 0.00 0.00 0.00 * 0.03 | - - n/a n/a SingleSource/UnitTests/2007-03-02-VaCopy | 0.0000 796 0.0040 * 0.0040 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a SingleSource/UnitTests/2007-04-10-BitfieldTest | 0.0040 548 0.0000 * 0.0040...

LLVMers, The 2.2 prerelease is now available for testing: http://llvm.org/prereleases/2.2/ If anyone can help test this release, I ask that you do the following: 1) Build llvm and llvm-gcc (or use a binary). You may build release (default) or debug. You may pick llvm-gcc-4.0, llvm-gcc-4.2, or both. 2) Run 'make check'. 3) In llvm-test, run 'make TEST=nightly report'. 4) When

...* 0.04 | - - n/a n/a SingleSource/UnitTests/2007-01-04-KNR-Args | 0.0090 608 0.0024 * 0.0024 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a SingleSource/UnitTests/2007-03-02-VaCopy | 0.0083 792 0.0026 * 0.0025 | 0.00 0.00 0.00 * 0.02 | - - n/a n/a SingleSource/UnitTests/2007-04-10-BitfieldTest | 0.0027 540 0.0015 * 0.0015...

...* 0.04 | - - n/a n/a SingleSource/UnitTests/2007-01-04-KNR-Args | 0.0015 640 0.0017 * * | 0.00 0.00 0.00 * * | - - n/a n/a SingleSource/UnitTests/2007-03-02-VaCopy | 0.0016 1040 0.0025 * 0.0025 | 0.00 * 0.00 * 0.00 | n/a - n/a n/a SingleSource/UnitTests/2007-04-10-BitfieldTest | 0.0008 568 0.0010 * 0.0011...

...04 | -       -       n/a          n/a > SingleSource/UnitTests/2007-01-04-KNR-Args                               | > 0.0000 668      0.0000      *                0.0000      |    0.00    0.00 >  0.00 *           0.01 | -       -       n/a          n/a > SingleSource/UnitTests/2007-03-02-VaCopy                                 | > 0.0100 944      0.0100      *                0.0000      |    0.01    0.00 >  0.01 *           0.02 | -       -       n/a          n/a > SingleSource/UnitTests/2007-04-10-BitfieldTest                           | > 0.0100 604      0.0000      *        ...

Hi Tanya, > 1) Compile llvm from source and untar the llvm-test in the projects > directory (name it llvm-test or test-suite). Choose to use a > pre-compiled llvm-gcc or re-compile it yourself. I compiled llvm and llvm-gcc with separate objects directories. Platform is x86_64-linux-gnu. > 2) Run make check, report any failures (FAIL or unexpected pass). Note > that you need to

...n/a n/a > SingleSource/UnitTests/2007-01-04-KNR- > Args | 0.0000 668 0.0000 > * 0.0000 | 0.00 0.00 0.00 * > 0.01 | - - n/a n/a > SingleSource/UnitTests/2007-03-02- > VaCopy | 0.0100 944 0.0100 > * 0.0000 | 0.01 0.00 0.01 * > 0.02 | - - n/a n/a > SingleSource/UnitTests/2007-04-10- > BitfieldTest | 0.0100 604 0.0000...

LLVMers, The 2.1 pre-release (version 1) is available for testing: http://llvm.org/prereleases/2.1/version1/ I'm looking for members of the LLVM community to test the 2.1 release. There are 2 ways you can help: 1) Download llvm-2.1, llvm-test-2.1, and the appropriate llvm-gcc4.0 binary. Run "make check" and the full llvm-test suite (make TEST=nightly report). 2) Download

LLVMers, 2.6 pre-release2 is ready to be tested by the community. http://llvm.org/prereleases/2.6/ If you have time, I'd appreciate anyone who can help test the release. To test llvm-gcc: 1) Compile llvm from source and untar the llvm-test in the projects directory (name it llvm-test or test-suite). Choose to use a pre- compiled llvm-gcc or re-compile it yourself. 2) Run make check,

LLVMers, The 2.5 pre-release is available for testing: http://llvm.org/prereleases/2.5/ If you have time, I'd appreciate anyone who can help test the release. Please do the following: 1) Download/compile llvm source, and either compile llvm-gcc source or use llvm-gcc binary (please compile llvm-gcc with fortran if you can). 2) Run make check, send me the testrun.log 3) Run "make

Hi Stepan, Sorry for the delay. It's great that you are working on MergeFunctions as well and I agree, we should definitely try to combine our efforts to improve MergeFunctions. Just to give you some context, the pass (with the similar function merging patch) is already being used in a production setting. From my point of view, it would be better if we focus on improving its capability

...t_varg.ll 1 1864 0 0.01 1855 0 0.01 1855 2006-12-04-DynAllocAndRestore.ll 5 7012 0 0.01 7001 0 0.01 7001 2006-12-07-Compare64BitConstant.ll 1 2532 0 0.01 2523 0 0.01 2523 2006-12-11-LoadConstants.ll 155 38553 0 0.02 38544 0 0.01 38544 2007-01-04-KNR-Args.ll 3 5681 0 0.01 5672 0 0.01 5672 2007-03-02-VaCopy.ll 2 4199 0 0.01 4190 0 0.01 4190 2007-04-10-BitfieldTest.ll 1 2325 0 0.01 2316 0 0.01 2316 2007-04-25-weak.ll 1 1941 0 0.01 1932 0 0.01 1932 2008-01-07-LongDouble.ll 1 1693 0 0.01 1681 0 0.01 1681 2008-01-29-ParamAliasesReturn.ll 5 7207 0 0.01 7191 0 0.01 7191 2008-04-18-LoopBug.ll 2 5876 0 0.01 5...