Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.arch.embedded > #27657

Re: A new benchmark suitable for small systems: stdcbench

From Philipp Klaus Krause <pkk@spth.de>
Newsgroups comp.arch.embedded
Subject Re: A new benchmark suitable for small systems: stdcbench
Date 2018-02-21 09:29 +0100
Organization solani.org
Message-ID <p6jalq$qm6$1@solani.org> (permalink)
References (5 earlier) <062d7d94-2806-4f08-99b2-652a5d57da21@googlegroups.com> <p6h8c3$h4o$1@solani.org> <p6hb88$j84$1@solani.org> <p6hukc$142$1@solani.org> <33132e56-08c6-4514-bdce-052ed44d6dd2@googlegroups.com>

Show all headers | View raw


Am 21.02.2018 um 08:37 schrieb raimond.dragomir@gmail.com:
>> And from the opposite end of the performance spectrum, a Cycpress EZ-USB
>> FX2LP at 48 Mhz, compiled using SDCC 3.7.0 RC2, sdcc -mmcs51
>> --model-large --stack-auto --code-loc 0x0000 --code-size 0x3500
>> --xram-loc 0x3500 --xram-size 0x0b00 --opt-code-speed
>> --max-allocs-per-node 10000:
>>
>> stdcbench 0.3
>> stdcbench c90base score: 12
>> stdcbench final score: 12
>>
>> Philipp
> 
> Is it 12clk/instruction or something? In this case 48MHz is misleading.
> Same for PICs which are 4clks/instr. Microchip usually give another
> number, the Mips, for example 64MHz/16Mips.
> 
> So the Cypress chips is 48MHz/4Mips maybe?
> 
> When I worked with 12clks/instr 8051 I always talked about it as 1Mips cpu.
> 

The Cypress EZ-USB can execute most 1-byte instructions in 4 clock
cycles. Most 2-byte instructions take 8 clock cycles. Branch
instructions tend to take 16 clock cycles. A few instrcutions take even
longer.

I gave the 48 Mhz figure mostly for reproduction of results (though the
port can be found in the examples for stdcbench now anyway).

Philipp

Back to comp.arch.embedded | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

A new benchmark suitable for small systems: stdcbench Philipp Klaus Krause <pkk@spth.de> - 2018-02-07 16:49 +0100
  Re: A new benchmark suitable for small systems: stdcbench raimond.dragomir@gmail.com - 2018-02-08 22:36 -0800
    Re: A new benchmark suitable for small systems: stdcbench Philipp Klaus Krause <pkk@spth.de> - 2018-02-09 20:48 +0100
      Re: A new benchmark suitable for small systems: stdcbench Paul Rubin <no.email@nospam.invalid> - 2018-02-09 13:28 -0800
        Re: A new benchmark suitable for small systems: stdcbench Stef <stef33d@yahooI-N-V-A-L-I-D.com.invalid> - 2018-02-10 01:26 +0100
        Re: A new benchmark suitable for small systems: stdcbench Philipp Klaus Krause <pkk@spth.de> - 2018-02-10 18:47 +0100
          Re: A new benchmark suitable for small systems: stdcbench Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2018-02-10 21:32 +0200
            Re: A new benchmark suitable for small systems: stdcbench Philipp Klaus Krause <pkk@spth.de> - 2018-02-10 20:40 +0100
        Re: A new benchmark suitable for small systems: stdcbench Philipp Klaus Krause <pkk@spth.de> - 2018-02-20 14:00 +0100
          Re: A new benchmark suitable for small systems: stdcbench raimond.dragomir@gmail.com - 2018-02-20 05:13 -0800
            Re: A new benchmark suitable for small systems: stdcbench Philipp Klaus Krause <pkk@spth.de> - 2018-02-20 14:38 +0100
              Re: A new benchmark suitable for small systems: stdcbench Philipp Klaus Krause <pkk@spth.de> - 2018-02-20 15:27 +0100
                Re: A new benchmark suitable for small systems: stdcbench Jack <jack4747@gmail.com> - 2018-02-20 07:14 -0800
                Re: A new benchmark suitable for small systems: stdcbench Philipp Klaus Krause <pkk@spth.de> - 2018-02-20 17:30 +0100
                Re: A new benchmark suitable for small systems: stdcbench Philipp Klaus Krause <pkk@spth.de> - 2018-03-05 19:59 +0100
                Re: A new benchmark suitable for small systems: stdcbench Philipp Klaus Krause <pkk@spth.de> - 2018-02-20 20:58 +0100
                Re: A new benchmark suitable for small systems: stdcbench raimond.dragomir@gmail.com - 2018-02-20 23:37 -0800
                Re: A new benchmark suitable for small systems: stdcbench Philipp Klaus Krause <pkk@spth.de> - 2018-02-21 09:29 +0100
                Re: A new benchmark suitable for small systems: stdcbench David Brown <david.brown@hesbynett.no> - 2018-02-21 11:01 +0100
          Re: A new benchmark suitable for small systems: stdcbench Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2018-02-20 21:37 +0200
            Re: A new benchmark suitable for small systems: stdcbench raimond.dragomir@gmail.com - 2018-02-20 23:42 -0800
      Re: A new benchmark suitable for small systems: stdcbench raimond.dragomir@gmail.com - 2018-02-10 22:48 -0800
        Re: A new benchmark suitable for small systems: stdcbench Paul Rubin <no.email@nospam.invalid> - 2018-02-11 13:22 -0800
      stdcbench STM8 compiler comparison Philipp Klaus Krause <pkk@spth.de> - 2018-02-11 19:20 +0100
        Re: stdcbench STM8 compiler comparison Grant Edwards <invalid@invalid.invalid> - 2018-02-11 23:29 +0000
          Re: stdcbench STM8 compiler comparison Philipp Klaus Krause <pkk@spth.de> - 2018-02-12 07:13 +0100

csiph-web