search for: npb

...s are computed in the main function (only a part of the main function is shown below) ############################################################### # quantities for bootstrap confidence intervals ############################################################### r.value<- cor(x,y) npb.B <- mean(r)-r.value npb.mean <- mean(r) npb.var <- var(r) r.star <- sort(r) z.star <- (r.star - mean(r.star))/sqrt(var(r.star)) after which the main function calls the function (i.s.conf.int) shown below, which is saved in a different script file ###############...

...ples covering some of the topics? Or may be >> someone knows good examples due to the fact that current register >> allocators perform too bad on it? ;-) > > I've found the NAS Parallel Benchmarks to be quite a good workout: > > http://www.nas.nasa.gov/Resources/Software/npb.html > > They are medium-sized benchmarks, so substantial without being totally > overwhelming. They manifest pretty much all of your points above. > The > basic linear scan algorithm seems to do fairly well on them so it > makes > for a good comparison. > > I use v...

On Apr 2, 2008, at 9:58 PM, Chris Lattner wrote: > > Could these be added to llvm-test? > > -Chris I just added the two C benchmarks as MultiSource/Benchmarks/NPB-serial. --Owen -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2555 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080403/e41bd836/attachment.bin>

...r of entries "IPC$ nobody nobody" which we did not see in 2.0.7. Is this normal in 2.2.5 or something I should be ivestigating? Eg trout# smbstatus Samba version 2.2.5 Service uid gid pid machine ---------------------------------------------- dar3338$ npb ports 4109 beldon (192.9.202.168) Fri Aug 16 12:30:21 2002 der3339$ rbe hm 3828 ettrick (192.9.202.246) Fri Aug 16 09:02:23 2002 ddr3325$ hai rpu 3997 leith (192.9.202.150) Fri Aug 16 11:58:58 2002 IPC$ nobody nobody 3828 ettrick (...

...; found a good set of examples covering some of the topics? Or may be > someone knows good examples due to the fact that current register > allocators perform too bad on it? ;-) I've found the NAS Parallel Benchmarks to be quite a good workout: http://www.nas.nasa.gov/Resources/Software/npb.html They are medium-sized benchmarks, so substantial without being totally overwhelming. They manifest pretty much all of your points above. The basic linear scan algorithm seems to do fairly well on them so it makes for a good comparison. I use version 2.3, the serial flavor (yes, I understan...

Hi, As I mentioned some time ago on the mailing list, I'm working on the implementation of the Sarkar's Extended Linear Scan algorithm for LLVM. For testing and debugging of this algorithm, I need some good test-cases that check different functionalities of the register allocator, e.g.: - test-cases involving a lot of spilling - test-cases using pre-colored registers, e.g. like the EAX

...ups: comp.security.ssh >Subject: Re: Q: core dumped on keygen in Sol 2.6, ssh2.3.0p1, openssl-0.9.6 and zlib-1.1.3 >Date: 21 Feb 2001 12:27:24 +0000 >Organization: University of Glasgow >Lines: 52 >Message-ID: <uv7l2knrv7.fsf at slicker.dcs.gla.ac.uk> >References: <9578vs$npb$1 at nnrp1.deja.com> >NNTP-Posting-Host: slicker.dcs.gla.ac.uk >Mime-Version: 1.0 >Content-Type: text/plain; charset=us-ascii >X-Trace: singer.cent.gla.ac.uk 982758493 8576 130.209.242.51 (21 Feb 2001 12:28:13 GMT) >X-Complaints-To: newsmaster at gla.ac.uk >NNTP-Posting-Date: 2...

On 30/04/2014 16:20, Yi Kong wrote: > Hi Tobias, Renato, > > Thanks for your attention to my RFC. > On 30 April 2014 07:50, Tobias Grosser <tobias at grosser.es> wrote: > >> - Show and graph total compile time > >> There is no obvious way to scale up the compile time of > >> individual benchmarks, so total time is the best thing we can do to >

Hi all, I've started looking at the GlobalMerge pass, enabled by default on ARM and AArch64. I think we should reconsider that, at least for AArch64. As is, the pass just merges all globals together, in groups of 4KB (AArch64, 128B on ARM). At the time it was enabled, the general thinking was "it's almost free, it doesn't affect performance much, we might as well use it".

...MultiSource/Benchmarks/llubenchmark/llu | * | * | MultiSource/Benchmarks/sim/sim | * | * | MultiSource/Benchmarks/tramp3d-v4/tramp3d-v4 | * | * | MultiSource/Benchmarks/NPB-serial/is/is | * | * | MultiSource/Benchmarks/Bullet/bullet | * | * | MultiSource/Benchmarks/McCat/03-testtrie/testtrie | * | * | MultiSource/Benchmarks/McCat/12-IOtest/iotest...

...1.8853 2.66281855804835 Benchmarks/McCat/08-main/main 0.0138 0.0142 2.89855072463769 Applications/siod/siod 1.8991 1.9696 3.71228476646833 Benchmarks/FreeBench/distray/distray 0.0793 0.0829 4.53972257250947 Benchmarks/NPB-serial/is/is 4.6101 4.8299 4.76779245569511 Applications/kimwitu++/kc 0.0266 0.0279 4.88721804511279 Benchmarks/Olden/mst/mst 0.0551 0.0589 6.89655172413793 Benchmarks/Ptrdist/yacr2/yacr2 0.5277...

Andy and I briefly discussed this the other day, we have not yet got chance to list a detailed pass order for the pre- and post- IPO scalar optimizations. This is wish-list in our mind: pre-IPO: based on the ordering he propose, get rid of the inlining (or just inline tiny func), get rid of all loop xforms... post-IPO: get rid of inlining, or maybe we still need it, only

...180732945|0.024456293| -0.17| 180732955| 0|0.024469807| -0.22| 180732955| 0| |MultiSource/Benchmarks/MiBench/telecomm-gsm/telecomm-gsm.test | 244|0.091691314| 929866173|0.091410543| 0.31| 929851703| 0|0.091484827| 0.23| 929851702| 0| |MultiSource/Benchmarks/NPB-serial/is/is.test | 40|4.489582746|11646133712| 4.49184759| -0.05|11612579256| 0.29|4.491813371| -0.05|11612579254| 0.29| |MultiSource/Benchmarks/Olden/bh/bh.test | 39|0.929609207| 3751128971|0.927774549| 0.2| 37511289...

...        0.02 | -       -       n/a          n/a > MultiSource/Benchmarks/MiBench/telecomm-gsm/telecomm-gsm                 | > 0.3500 76716    0.3299      *                0.1900      |    0.23    0.24 >  0.23 *           0.43 | 0.96    1.00    n/a          n/a > MultiSource/Benchmarks/NPB-serial/is/is                                  | > 0.0099 5116     0.0300      *                0.3599      |   10.08    9.85 >  9.84 *          10.18 | 1.02    1.02    n/a          n/a > MultiSource/Benchmarks/Olden/bh/bh                                       | > 0.1199 15308    0.0800...

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 > MultiSource/Benchmarks/MiBench/telecomm-gsm/telecomm- > gsm | 0.3500 76716 0.3299 * > 0.1900 | 0.23 0.24 0.23 * 0.43 | 0.96 > 1.00 n/a n/a > MultiSource/Benchmarks/NPB-serial/is/ > is | 0.0099 5116 0.0300 > * 0.3599 | 10.08 9.85 9.84 * > 10.18 | 1.02 1.02 n/a n/a > MultiSource/Benchmarks/Olden/bh/ > bh | 0.1199 1...

...> > 1.66% 0.1024 0.1041 0.0002 > MultiSource/Applications/JM/lencod/lencod.compile > <http://llvm.org/perf/db_default/simple/nts/380/graph?pset.0=on&test.MultiSource%2FApplications%2FJM%2Flencod%2Flencod.compile=on> > 1.66% 15.2642 15.5174 0.0333 > MultiSource/Benchmarks/NPB-serial/is/is.compile > <http://llvm.org/perf/db_default/simple/nts/380/graph?pset.0=on&test.MultiSource%2FBenchmarks%2FNPB-serial%2Fis%2Fis.compile=on> > 1.65% 0.0726 0.0738 0.0003 > SingleSource/Benchmarks/Misc-C++/stepanov_container.compile > <http://llvm.org/perf/db_defa...

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

...at CuD-(1J%+7&o*Ja7+_>zVblWRl76X9svPHYila0`Q zi%)=oy=0P4Cmq17|JRa2*8&ecCx_R{sP0C#nfb__G at M<RnMy2AMv^4Zw?s0TM^%b9 z$;N)sF&G(6+1`QZD*_pzZaCwkz_5AQFe4^86ERlK-a9M+(T{<+s<ED-BQLd^Tb_8; z8ee8zUKzZbZev+C<5;^m>D6{8?@5Slz|wm)yQFhVE+P<p<o{PT=Zg!?LH(Oba=SL` zkdIr%PEMJ$+|inpBm;rfxUm(}oM1gf*<}twR*)nr1TZ?70_%7CM%Keb+j9mP%dga( z6IE1ZUYdyNeL93~w#kpMOexy;mH>M;v-t8pv5J81GWn}cR&PC<1 at A`zc9!&ZB7Vmd ze%}Ld^_- at j3Or3$D&y)I`I)EW+>$HApC%ACuBy4C$qf4y(?J^fA=dN;whuU2-^C at _ z1xTSy0di^;@aumxB1R_(EJ@{``%+xN8T%krK$c6IdE3fUdl~7&g0&rKx<!WGF9AHN z*Ql3...