From: Alan Modra <amodra@bigpond.net.au>
To: Zack Weinberg <zack@codesourcery.com>
Cc: binutils@sources.redhat.com, hans-peter.nilsson@axis.com
Subject: Re: [RFA:] Fix bug with #APP/#NO_APP when using macros.
Date: Fri, 09 May 2003 04:38:00 -0000 [thread overview]
Message-ID: <20030509043813.GB2166@bubble.sa.bigpond.net.au> (raw)
In-Reply-To: <87el38zs39.fsf@egil.codesourcery.com>
On Thu, May 08, 2003 at 09:01:14PM -0700, Zack Weinberg wrote:
> And since no one has noticed this up to now, does that mean that there
> is no real performance benefit to be had from #NO_APP, and we can blow
> away all the code that emits it from gcc? Or should gcc be changed to
> emit #NO_APP at file start?
I just ran a current assembler (without HPAs latest patch) on a
powerpc-linux insn-attrtab.s which happens to be well over 6M in
size.
Without #NO_APP (I used #NO-APP :))
real 0m2.450s
user 0m2.370s
sys 0m0.090s
With #NO_APP
real 0m1.917s
user 0m1.850s
sys 0m0.060s
To put these numbers into context, gcc -g took nearly 20 seconds to
produce the .s file. ie. the assembly time improvement gained by
adding #NO_APP represents about 2.6% of the total time to produce the
object file. For a -g -O2 compile the improvement was only 0.86%.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2003-05-09 4:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 8:08 Hans-Peter Nilsson
2003-05-08 21:39 ` Ian Lance Taylor
2003-05-09 1:09 ` Hans-Peter Nilsson
2003-05-09 3:39 ` Ian Lance Taylor
2003-05-09 4:01 ` Zack Weinberg
2003-05-09 4:12 ` Ian Lance Taylor
2003-05-09 4:38 ` Alan Modra [this message]
2003-05-09 9:10 ` Hans-Peter Nilsson
2003-05-09 9:28 ` Hans-Peter Nilsson
2003-05-13 1:09 ` Hans-Peter Nilsson
2003-05-13 1:27 ` Alan Modra
2003-05-13 2:39 ` Daniel Jacobowitz
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=20030509043813.GB2166@bubble.sa.bigpond.net.au \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=hans-peter.nilsson@axis.com \
--cc=zack@codesourcery.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).