From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Willy Tarreau <w@1wt.eu>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Dhrystone -- userland version
Date: Mon, 9 Jan 2023 20:57:30 +0100 [thread overview]
Message-ID: <CAMuHMdX-xpu-+8kAun90ZdYLe6kMzW3CEoD_hQtpwTPSJ8Tp1A@mail.gmail.com> (raw)
In-Reply-To: <20230109143059.GB25476@1wt.eu>
Hi Willy,
On Mon, Jan 9, 2023 at 3:31 PM Willy Tarreau <w@1wt.eu> wrote:
> Then maybe you'd rather use this:
>
> https://github.com/wtarreau/mhz
> It's also what's used by sbc-bench to verify that CPU vendors are not
> cheating in the embedded world. It's very simple, and not arch-dependent
> nor compiler-dependent (at least as long as you don't build at -O0 :-)).
Gcc 4.1.2 (still the userspace compiler on a few of my old systems)
doesn't like the aligned() attribute on functions.
In glibc 2.3, LLONG_MAX is defined conditionally on __USE_ISOC99.
Apart from that, the result is fairly accurate. Nice job!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2023-01-09 19:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 22:30 Dhrystone -- userland version Pavel Machek
2023-01-08 5:16 ` Theodore Ts'o
2023-01-08 7:40 ` Pavel Machek
2023-01-08 9:58 ` Geert Uytterhoeven
2023-01-08 18:47 ` Pavel Machek
2023-01-09 0:45 ` Theodore Ts'o
2023-01-09 9:28 ` Geert Uytterhoeven
2023-01-09 14:30 ` Willy Tarreau
2023-01-09 19:36 ` Geert Uytterhoeven
2023-01-09 19:51 ` Pavel Machek
2023-01-09 19:59 ` Geert Uytterhoeven
2023-01-09 21:36 ` Willy Tarreau
2023-01-09 19:57 ` Geert Uytterhoeven [this message]
2023-01-09 14:59 ` Pavel Machek
2023-01-11 13:32 ` Jan Engelhardt
2023-01-11 13:52 ` Geert Uytterhoeven
2023-01-11 15:30 ` Pavel Machek
2023-01-11 16:32 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMuHMdX-xpu-+8kAun90ZdYLe6kMzW3CEoD_hQtpwTPSJ8Tp1A@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tytso@mit.edu \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.