Re: time(1) incorrect (Re) ... times(3) strange; clock

Re: time(1) incorrect (Re) ... times(3) strange; clock_t ==

Nigel Metheringham (Nigel.Metheringham@theplanet.net)
Thu, 29 Feb 1996 15:31:46 +0000

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Erik Troan: "Re: time(1) incorrect (Re) ... times(3) strange; clock_t == long"
Previous message: Locatelli Dario: "Linux/Alpha on XL-266"

craig@metrolink.com said:
} Speaking of the Byte benchmarks, I fixed the "write an long, read an
} int" problem in the pipe-based context switch test and sent diffs to
} the maintainer of the Linux Benchmark page. The response I got was

} > The code doesn't require a patch, BTW. Thousands have ran the code.

} Oh well. My mistake I'm sure.

Words fail me!
Its broken code. It should never have run, it just happens to by a
fluke of machine architecture. The man (or woman) who responded that
way is a jerk!

Nigel.

-- 
[ Nigel.Metheringham@theplanet.net   - Unix Applications Engineer ]
[ *Views expressed here are personal and not supported by PLAnet* ]
[ PLAnet Online : The White House     Tel : +44 113 2345566 x 612 ]
[ Melbourne Street, Leeds LS2 7PS UK. Fax : +44 113 2345656       ]

Next message: Erik Troan: "Re: time(1) incorrect (Re) ... times(3) strange; clock_t == long"
Previous message: Locatelli Dario: "Linux/Alpha on XL-266"