public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Ilija Kocho <ilijak@siva.com.mk>
Cc: Grant Edwards <grant.b.edwards@gmail.com>,
	ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Re: eCos arm-eabi GNU tools - test release 4.6.2-20120125
Date: Fri, 24 Feb 2012 21:10:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.00.1202242351080.19578@vostro> (raw)
In-Reply-To: <4F47F59E.7070201@siva.com.mk>

On Fri, 24 Feb 2012, Ilija Kocho wrote:

> On 24.02.2012 20:37, Grant Edwards wrote:
> 
> [snip]
> 
> > [I was hoping the 3.2->4.6 change might produce noticably smaller or
> > faster code.  The size reduction is about 0.8%, and though I haven't
> > done any extensive benchmarking, I haven't noticed any speed
> > improvement yet.]
> 
> I haven't compared against 3.2.
> 
> Regarding speed, for Cortex-M3 target the Coremark test shows 12%
> speed up of 4.6.2 against 4.3.2. But Cortex-M runs Thumb2 instruction
> set, the picture may be different for ARM code.

I call that I had got more dry & whet mips on my arm7tdmi target when I
s/3.2.1/4.3.2/

Fortunately, I found my old ask (and results for 3.2.1) on the list :-)
http://sourceware.org/ml/ecos-discuss/2006-12/msg00000.html

Just now I tried 'dhrystone' test for 4.6.2. Well, I know issues with
this test, but ...

I got

  22 VAX MIPS (GCC 4.6.2) vs 13 VAX MIPS (GCC 3.2.1) for RAM startup

and

  34 VAX MIPS (GCC 4.6.2) vs 22 VAX MIPS (GCC 3.2.1) for ROM startup
  (on-chip flash).

IMHO, it is nice delta. Of course, it is true for my arm7tdmi target and
may be you will get more modest results for your one.

Sergei

> 
> Ilija
> 
> -- 
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
> 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2012-02-24 20:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13 21:58 [ECOS] " John Dallaway
2012-02-24 19:00 ` [ECOS] " Grant Edwards
2012-02-24 19:37   ` Ilija Kocho
2012-02-24 20:15     ` Grant Edwards
2012-02-24 20:53       ` Ilija Kocho
2012-02-24 21:10         ` Sergei Gavrikov [this message]
2012-02-29 20:45       ` Grant Edwards
2012-03-02  0:35       ` Grant Edwards
2012-02-24 20:40   ` Sergei Gavrikov
2012-02-24 21:38     ` Grant Edwards
2012-02-24 22:05       ` Sergei Gavrikov
2012-02-25  8:39         ` Grant Edwards
2012-02-28  8:23           ` Sergei Gavrikov
2012-02-29 21:59             ` Grant Edwards
2012-03-01  7:25               ` Sergei Gavrikov
2012-03-01 14:32                 ` Grant Edwards

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=alpine.DEB.2.00.1202242351080.19578@vostro \
    --to=sergei.gavrikov@gmail.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=grant.b.edwards@gmail.com \
    --cc=ilijak@siva.com.mk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).