Re: Benchmark recommendations needed

2022-02-23 Thread andras
On 2022-02-22 16:59, Patrick McGehearty wrote: I studied Dhrystone about 30 years ago and found it had a number of flaws back then. For example, most of the loops in the code are only executed 1-3 times, which minimizes the value of hoisting values out of inner loops. Read the Dhrystone wikipedia

Re: Benchmark recommendations needed

2022-02-22 Thread Patrick McGehearty
I studied Dhrystone about 30 years ago and found it had a number of flaws back then. For example, most of the loops in the code are only executed 1-3 times, which minimizes the value of hoisting values out of inner loops. Read the Dhrystone wikipedia article for more information. Going back to wh

Re: Benchmark recommendations needed

2022-02-22 Thread Paul Koning via Gcc
> On Feb 22, 2022, at 4:26 PM, Gary Oblock via Gcc wrote: > > Andras, > > The whole point of benchmarks is to judge a processor's performance. > That being said, just crippling GCC is not reasonable because > processors must be judged in the appropriate context and that > includes the current

Re: Benchmark recommendations needed

2022-02-22 Thread Gary Oblock via Gcc
r I'd benchmark it using the applications you built it for. Gary From: Andras Tantos Sent: Monday, February 21, 2022 9:22 PM To: Gary Oblock ; gcc@gcc.gnu.org Subject: Re: Benchmark recommendations needed [EXTERNAL EMAIL NOTICE: This email originated from a

Re: Benchmark recommendations needed

2022-02-22 Thread Richard Earnshaw via Gcc
Dhrystone is (and probably always was) a bogus benchmark. It's a well-known truism that MIPS stands for Meaningless Indication of Processor Speed, and dhrystone scores are equally meaningless. Dhrystone fell out of common usage over 20 years ago. It's not GCC that is being peculiar, it's just

Re: Benchmark recommendations needed

2022-02-21 Thread Andras Tantos
That's true, I did notice GCC being rather ... peculiar about drhystone. Is there a way to make it less clever about the benchmark? Or is there some alteration to the benchmark I can make to not trigger the special behavior in GCC? Andras On Mon, 2022-02-21 at 03:19 +, Gary Oblock via Gcc wr

Re: Benchmark recommendations needed

2022-02-20 Thread Gary Oblock via Gcc
Trying to use the dhrystone isn't going to be very useful. It has many downsides not the least is that gcc's optimizer can run rings about it. Gary From: Gcc on behalf of gcc-requ...@gcc.gnu.org Sent: Tuesday, February 15, 2022 6:25 AM To: gcc@gcc.gnu.org Sub

Re: Benchmark recommendations needed

2022-02-17 Thread andras
Thanks H-P! I'll certainly check it out. Andras February 17, 2022 9:15 AM, "Hans-Peter Nilsson" wrote: > On Mon, 14 Feb 2022, Andras Tantos wrote: > >> Hello all! >> >> I'm working on porting GCC to a new processor architecture. I think >> I've finally got to a fairly stable stage, so the nex

Re: Benchmark recommendations needed

2022-02-17 Thread Hans-Peter Nilsson
On Mon, 14 Feb 2022, Andras Tantos wrote: > Hello all! > > I'm working on porting GCC to a new processor architecture. I think > I've finally got to a fairly stable stage, so the next logical step > would be to test and optimize. For that, I would need some benchmarks, > and this is where I'm seeki

Re: Benchmark recommendations needed

2022-02-15 Thread Richard Biener via Gcc
On Tue, Feb 15, 2022 at 3:25 PM Andras Tantos wrote: > > Hello all! > > I'm working on porting GCC to a new processor architecture. I think > I've finally got to a fairly stable stage, so the next logical step > would be to test and optimize. For that, I would need some benchmarks, > and this is w

Benchmark recommendations needed

2022-02-15 Thread Andras Tantos
Hello all! I'm working on porting GCC to a new processor architecture. I think I've finally got to a fairly stable stage, so the next logical step would be to test and optimize. For that, I would need some benchmarks, and this is where I'm seeking your help. This being a hobby project, I can't sh