17 Feb
2022
17 Feb
'22
10:38 p.m.
Damn, you guys found a bug in my venix emulation:
% echo 99k2vp8opq | ./git/venix/tools/vm86venix/venix
./git/venix/tools/vm86venix/disbt/usr/bin/dc
pid 70803 (venix): sigreturn eflags = 0x0
I'll have to see how hard it is to setup my Rainbow 100B running Venix and
if the benchmark works there or not.
Or if this is a bug in venix's dc...
Warner
On Thu, Feb 17, 2022 at 9:33 AM Andrew Hume <andrew(a)humeweb.com> wrote:
altho i date back to those days, i don’t recall using
that benchmark.
when i’ve needed something bc-ish to take some time, i normally
use a bessel function from bc -l
On Feb 17, 2022, at 2:24 AM, Andy Kosela
<akosela(a)andykosela.com> wrote:
On Wed, Feb 16, 2022 at 11:42 PM Andrew Diller <dillera(a)gmail.com>
wrote:
>
>
>
>> On Feb 16, 2022, at 5:27 PM, Dave Horsfall <dave(a)horsfall.org> wrote:
>>
>> On Wed, 16 Feb 2022, Leah Neukirchen wrote:
>>
>>> Apparently it was a popular benchmark back in the day:
>>> https://www.tuhs.org/Archive/Documentation/AUUGN/AUUGN-V05.1.pdf
>>
>> Yep.
>>
>>>> The benchmark was "echo 99k2vp8opq I /bin/time dc > /dev/null’.
It
>>>> uses dc (the desk calculator) to calculate the square root of 2 to 99
>>>> decimal places,
>>
>
> I tried that on some of the systems I have at hand. It didn't even
register on my Mac....
This would be more appropriate on modern machines:
moon $ sysctl machdep.cpu.brand_string; echo 9999k2vp8opq | time -p dc
/dev/null
machdep.cpu.brand_string:
Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz
real 1.87
user 1.87
sys 0.00
--Andy