search for: pointer_method

...he __cxa.* functions are not found (bei llc and when compiling c-backend code) (i guess thats what you were refering to) > > and a few other failures i did not relate to this 2 groups Right, C++ EH is disabled in llvm-gcc at this point. Some of the failures do look real though, things like pointer_method, BuiltinTypeInfo, ofstream_ctor, etc. Very nice. Reid/Anton, do you guys have an idea when the svn server will be available? -Chris -- http://nondot.org/sabre/ http://llvm.org/

hi > > i fixed some major bugs in the llvm-gcc4_2 patch since my last post. > > this brings me to an interesting question: > > > > what are your criteria to use my patch for further development? > > I have no fixed criteria. I think the best solution is for the work to be > checked into the (forthcoming) public SVN server. When it is available, > you can

...ce/Regression/C++/fixups SingleSource/Regression/C++/global_ctor SingleSource/Regression/C/globalrefs SingleSource/Regression/C++/global_type SingleSource/Regression/C++/ofstream_ctor SingleSource/Regression/C/pointer_arithmetic SingleSource/Regression/C++/pointer_member SingleSource/Regression/C++/pointer_method SingleSource/Regression/C++/pointer_method2 SingleSource/Regression/C/PR10189 SingleSource/Regression/C/PR1386 SingleSource/Regression/C/PR491 SingleSource/Regression/C/PR640 SingleSource/Regression/C++/short_circuit_dtor SingleSource/Regression/C/sumarray SingleSource/Regression/C/sumarraymalloc S...

...leSource/Regression/C++/BuiltinTypeInfo | * | * | SingleSource/Regression/C++/2003-05-14-expr_stmt | * | * | SingleSource/Regression/C++/2003-06-08-VirtualFunctions | * | * | SingleSource/Regression/C++/pointer_method2 | * | * | SingleSource/Regression/C++/pointer_method | * | * | SingleSource/Regression/C++/pointer_member | * | * | SingleSource/Regression/C++/2003-09-29-NonPODsByValue...

...0.00 * 0.01 | - - n/a n/a SingleSource/Regression/C++/pointer_member | 0.0023 556 0.0019 * 0.0019 | 0.00 0.00 0.00 * 0.00 | - - n/a n/a SingleSource/Regression/C++/pointer_method | 0.0071 1544 0.0068 * 0.0067 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a SingleSource/Regression/C++/short_circuit_dtor | 0.0077 768 0.0022 * 0.0022...

...0.00 * 0.03 | - - n/a n/a SingleSource/Regression/C++/pointer_member | 0.0040 580 0.0000 * 0.0040 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a SingleSource/Regression/C++/pointer_method | 0.0120 1580 0.0120 * 0.0080 | 0.01 0.00 0.00 * 0.02 | - - n/a n/a SingleSource/Regression/C++/short_circuit_dtor | 0.0080 904 0.0040 * 0.0000...

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.00 * 0.01 | - - n/a n/a SingleSource/Regression/C++/pointer_member | 0.0030 564 0.0015 * 0.0015 | 0.00 0.01 0.00 * 0.01 | - - n/a n/a SingleSource/Regression/C++/pointer_method | 0.0076 1564 0.0051 * 0.0052 | 0.00 0.00 0.00 * 0.02 | - - n/a n/a SingleSource/Regression/C++/short_circuit_dtor | 0.0045 892 0.0065 * 0.0018...

...0.00 * 0.00 | - - n/a n/a SingleSource/Regression/C++/pointer_member | 0.0009 580 0.0010 * 0.0010 | 0.00 0.00 0.00 * 0.00 | - - n/a n/a SingleSource/Regression/C++/pointer_method | 0.0033 2388 0.0036 * 0.0034 | 0.00 0.00 0.00 * 0.01 | - - n/a n/a SingleSource/Regression/C++/short_circuit_dtor | 0.0025 796 0.0012 * 0.0012...

...    0.04 | -       -       n/a          n/a > SingleSource/Regression/C++/pointer_member                               | > 0.0000 660      0.0000      *                0.0000      |    0.00    0.00 >  0.00 *           0.00 | -       -       n/a          n/a > SingleSource/Regression/C++/pointer_method                               | > 0.0000 664      0.0000      *                0.0100      |    0.00    0.00 >  0.00 *           0.01 | -       -       n/a          n/a > SingleSource/Regression/C++/short_circuit_dtor                           | > 0.0100 644      0.0100      *          ...

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/Regression/C++/ > pointer_member | 0.0000 660 > 0.0000 * 0.0000 | 0.00 0.00 0.00 > * 0.00 | - - n/a n/a > SingleSource/Regression/C++/ > pointer_method | 0.0000 664 > 0.0000 * 0.0100 | 0.00 0.00 0.00 > * 0.01 | - - n/a n/a > SingleSource/Regression/C++/ > short_circuit_dtor | 0.0100 644 > 0.0100...

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

...16483 0 0.01 16462 0 0.01 16462 plot.ll 7 123729 0 0.02 123700 0 0.02 123700 pmul.ll 1 19536 0 0.01 19509 0 0.01 19509 pneg.ll 1 7311 0 0.01 7284 0 0.01 7284 podd.ll 1 3991 0 0.01 3964 0 0.01 3964 pointer_arithmetic.ll 3 1706 1 0.01 1731 0 0.01 1694 pointer_member.ll 1 2820 0 0.01 2804 0 0.01 2804 pointer_method2.ll 12 17118 0 0.01 17102 0 0.01 17102 pointer_method.ll 4 5767 0 0.01 5751 0 0.01 5751 pointlis.ll 7 36345 0 0.01 36323 0 0.01 36323 point.ll 1 1705 0 0.01 1676 0 0.01 1676 point_relax.ll 12 306051 0 0.03 306022 0 0.03 305834 poisson.ll 1 2668 0 0.01 2646 0 0.01 2646 pops.ll 10 21600 0 0.01 21573...