public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Martin Guy <martinwguy@gmail.com>
Cc: "ng@piments.com" <ng@piments.com>,
		H Hartley Sweeten <hartleys@visionengravers.com>,
		crossgcc@sourceware.org
Subject: Re: crosstool-ng: cross compiler for -mach=arm4vt (Cirrus Logic  EP93xx target)
Date: Sat, 12 Sep 2009 20:18:00 -0000	[thread overview]
Message-ID: <20090912201825.GB10819@gmail.com> (raw)
In-Reply-To: <56d259a00909111520k671f2dfbja8f8ab2d2e6c2c94@mail.gmail.com>

On (11/09/09 23:20), Martin Guy wrote:
> On 9/11/09, ng@piments.com <ng@piments.com> wrote:
> >  I see you're posting patch sets for 4.2 and 4.3. I recall you said
> > somewhere that 4.2.x produced faster ARM code. Is that still your
> > experience?
> 
> THere's some extra measurements I didn't post there: using differen
> GCCs to compile gcc-4.3.4, and measuring the size of the different
> GCCs themselves and the size of the object code they generate and the
> maximum memory they use to do it (compiling insn_recog.c as a rule):
> 
>         --the compiler itself-- --on gcc-4.3.2 stage1--
> Version  gcc     cc1     cc1    Elapsed Max VM  xgcc
>          text    text    data   time    used    text
> gcc-3.4  79579  3862155   3236  4m30    104128  209509
> gcc-4.0  86429  4579965  10208  4m44    111104  225846
> gcc-4.1 193369  5115620  15976  4m56    123264  226469
> gcc-4.2 188582  5490547  17364  4m50    112128  221171
> gcc-4.3 203918* 7010746 420820  6m41    157440  227755
> gcc-4.4 202989* 9431805 546128  8m21    170550  249260
> llvm4.2 189365                  4m56     67136  236957

Did you compile exact same insn_recog.c source ?
if not then you are comparing apples to pineapples.

-Khem
> 
> so 4.2 shows an unexpected dip in its own size, its memory use, the
> time it takes to run and the size of its output code.
> (Maybe it was just gathering its strength for the exponential growth
> from 4.3 onwards :)
> 
>    M
> 
> --
> For unsubscribe information see http://sourceware.org/lists.html#faq
> 

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2009-09-12 20:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-08 22:48 H Hartley Sweeten
2009-09-09 11:01 ` Martin Guy
2009-09-09 18:06   ` H Hartley Sweeten
2009-09-09 19:26     ` wino
2009-09-11 19:33     ` Martin Guy
2009-09-11 21:57       ` ng
2009-09-11 22:12         ` wino
2009-09-11 22:20         ` Martin Guy
2009-09-12 20:18           ` Khem Raj [this message]
2009-09-13 13:15             ` Martin Guy
2009-09-13 15:55               ` Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2009-09-08 20:42 H Hartley Sweeten
2009-09-08 21:17 ` Yann E. MORIN
2009-09-08 21:31   ` Matthias Kaehlcke
2009-09-09  8:39 ` Steve Papacharalambous
2009-09-09 11:21   ` Martin Guy
2009-09-09 15:30     ` Steve Papacharalambous
2009-09-09 13:42 ` ng
2009-09-09 17:26   ` H Hartley Sweeten
2009-09-11 10:29     ` Martin Guy

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=20090912201825.GB10819@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=hartleys@visionengravers.com \
    --cc=martinwguy@gmail.com \
    --cc=ng@piments.com \
    /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).