Sponsored Content
Top Forums Programming Help with __builtin_prefetch function and it's timing Post 302261280 by fpmurphy on Monday 24th of November 2008 08:06:19 AM
Old 11-24-2008
AFAIK, it depends on your processor and the 'data' you are processing. Have you looked at prefetch test cases in the GCC testsuite (.../testsuite/gcc.misc-tests/i386- prefetch.exp)?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

timing a loop in unix.

hi guys.. i have a shell script that loops through a certain directory to see if a file has been created and then prints the file if it exists... the only problem i have now is that sometimes the flat does not get created by the program thats supposed to create it, in this scenario, my loop... (1 Reply)
Discussion started by: wolkott
1 Replies

2. UNIX for Advanced & Expert Users

scp timing out

having problems using scp in that during peak hours it appears to time out. anyone have similar experiences? any thoughts regarding a solution... (1 Reply)
Discussion started by: jph
1 Replies

3. Shell Programming and Scripting

Timing out a SSH

I need to make it so an autmated process which involves ssh, times out if ssh prompts for a password. Most of the time it shouldnt prompt for a password. But if it does i need it to time it out or get a status and stop the ssh and log that the ssh failed and move onto the next server. Is there any... (9 Replies)
Discussion started by: rcunn87
9 Replies

4. AIX

Kshell scripts and timing

Hello everyone, I have a script thats acting funky, what I would like to do is report to a file, how long its taking to get to certain area's, in seconds. For example. -- Start timer -- Run unix command 1 -- Run unix command 2 -- Stop timer -- Report Seconds -- etc etc Is there a way... (3 Replies)
Discussion started by: dbridle
3 Replies

5. Programming

timing your functions

hi everyone. If you have a function created in your code and you want to find out how long it takes for it to run you can use a struct called gettimeofday(). so lets say we have a function like this int myfunction (int r) { /*some math calculations*/ return answer; } How do i set up... (3 Replies)
Discussion started by: bebop1111116
3 Replies

6. Programming

Weird timing results in C

I was running some timings in my code to see which of several functions was the best and I've been getting some odd results. Here's the code I'm using: static double time_loop(int (*foo)(int)) { clock_t start, end; int n = 0, i = 0; start = clock(); for (; i <= MAXN; i++) if... (6 Replies)
Discussion started by: CRGreathouse
6 Replies

7. Shell Programming and Scripting

Timing a script

i have a very big script i have that i'd like to add a timeout to. this script runs on a several remote host. i update this script with timeout clause and then copy it over to all the hosts on which it is currently on. basically, i want the timeout to make the script abort/exit if it's... (1 Reply)
Discussion started by: SkySmart
1 Replies

8. Shell Programming and Scripting

Timing the shell script

I have two shell scripts, one written with xargs for parallel processing (p1) and the other written in old school way (p3) . when I execute them, i get the below values. $ time ./p1 real 0m25.36s user 0m0.32s sys 0m0.80s $ time ./p3 real 0m23.25s user 0m6.20s sys ... (4 Replies)
Discussion started by: luhah
4 Replies

9. Red Hat

Hardware and system timing are different

-> We have 2 servers server1 and server2 server. ->server1 is master application and server2 is slave application server. ->output of server1 hardware and slave timing: # hwclock --show Thu 05 Jun 2014 05:34:08 PM SGT -0.465666 seconds # date Thu Jun 5 17:34:16 SGT 2014 # cd... (6 Replies)
Discussion started by: manjusharma128
6 Replies

10. Programming

Byte swap timing

I have noticed the difference in byte swap timing between two Ubuntu systems. The bswap_32 used to work just fine on the old system, but on the new one it lags behind home-grown swap. My code: #include <stdio.h> #include <stdlib.h> #include <string.h> #include <byteswap.h> #include... (4 Replies)
Discussion started by: migurus
4 Replies
Test::Apocalypse(3pm)					User Contributed Perl Documentation				     Test::Apocalypse(3pm)

NAME
Test::Apocalypse - Apocalypse's favorite tests bundled into a simple interface SYNOPSIS
#!/usr/bin/perl use strict; use warnings; use Test::More; eval "use Test::Apocalypse"; if ( $@ ) { plan skip_all => 'Test::Apocalypse required for validating the distribution'; } else { # lousy hack for kwalitee require Test::NoWarnings; require Test::Pod; require Test::Pod::Coverage; is_apocalypse_here(); } ABSTRACT
Using this test module simplifies/bundles common distribution tests favored by the CPAN id APOCAL. DESCRIPTION
This module greatly simplifies common author tests for modules heading towards CPAN. I was sick of copy/pasting the tons of t/foo.t scripts + managing them in every distro. I thought it would be nice to bundle all of it into one module and toss it on CPAN :) That way, every time I update this module all of my dists would be magically updated! This module respects the TEST_AUTHOR env variable, if it is not set it will skip the entire testsuite. Normally end-users should not run it; but you can if you want to see how bad my dists are, ha! This module uses Module::Pluggable to have custom "backends" that process various tests. We wrap them in a hackish Test::Block block per- plugin and it seems to work nicely. If you want to write your own, it should be a breeze once you look at some of my plugins and see how it works. ( more documentation to come ) Usage In order to use this, you would need to be familiar with the "standard" steps in order to fully exercise the testsuite. There are a few steps we require, because our plugins need stuff to be prepared for them. For starters, you would need a test file in your distribution similar to the one in SYNOPSIS. Once that is done and added to your MANIFEST and etc, you can do this: perl Build.PL # sets up the dist ( duh, hah ) ./Build dist # makes the tarball ( so certain plugins can process it ) TEST_AUTHOR=1 ./Build test # runs the testsuite! EXPORT
Automatically exports the "is_apocalypse_here" sub. MORE IDEAS
o Document the way we do plugins so others can add to this testsuite :) o Per-plugin configuration for distros so we can override the default config o POD standards check Do we have SYNOPSIS, ABSTRACT, SUPPORT, etc sections? ( PerlCritic can do that! Need to investigate more... ) o Use Test::AutoLoader to check for .al files Br0ken install at this time... o Help with version updates automatically This little snippet helps a lot, I was wondering if I could integrate it into the testsuite hah! find -name '*.pm' | grep -v /blib/ | xargs sed -i "s/$VERSION = '[^']+?';/$VERSION = '0.05';/" o Use Test::GreaterVersion to sanity check versions The problem here is that I've got to learn the CPAN backend to extract the module name from the distro tarball, and pass it on to the test... o Use Test::PerlTidy to check code style Br0ken install at this time... ( PerlCritic can do that! Need to investigate more... ) o Integrate Test::UniqueTestNames into the testsuite This would be nice, but I'm not sure if I can actually force this on other tests. Otherwise I'll be just making sure that the Test::Apocalypse tests is unique, which is worthless to $dist trying to clean itself up... o META.yml checks We should make sure that the META.yml includes the "repository", "license", and other useful keys! o Other AUTHORs As always, we should keep up on the "latest" in the perl world and look at other authors for what they are doing. o indirect syntax We should figure out how to use indirect.pm to detect this deprecated method of coding. There's a Perl::Critic plugin for this, yay! SEE ALSO
None. SUPPORT
You can find documentation for this module with the perldoc command. perldoc Test::Apocalypse Websites o AnnoCPAN: Annotated CPAN documentation <http://annocpan.org/dist/Test-Apocalypse> o CPAN Ratings <http://cpanratings.perl.org/d/Test-Apocalypse> o RT: CPAN's request tracker <http://rt.cpan.org/NoAuth/Bugs.html?Dist=Test-Apocalypse> o Search CPAN <http://search.cpan.org/dist/Test-Apocalypse> o CPAN Testing Service <http://cpants.perl.org/dist/overview/Test-Apocalypse> Bugs Please report any bugs or feature requests to "bug-test-apocalypse at rt.cpan.org", or through the web interface at <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Test-Apocalypse>. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes. AUTHOR
Apocalypse <apocal@cpan.org> Thanks to jawnsy@cpan.org for the prodding and help in getting this package ready to be bundled into debian! COPYRIGHT AND LICENSE
Copyright 2009 by Apocalypse This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.10.1 2009-12-14 Test::Apocalypse(3pm)
All times are GMT -4. The time now is 02:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy