From: "Zagorodnev, Grigory" <grigory.zagorodnev@intel.com>
To: "Stas Kiselev" <stas_kiselev@bk.ru>, <binutils@sources.redhat.com>
Subject: RE: GAS
Date: Mon, 04 Apr 2005 16:03:00 -0000 [thread overview]
Message-ID: <F92C2EFE7C3BA745855BF7036E1F3F9AADBF10@NNSMSX401> (raw)
Stas,
Have you tried profiling gas to expose hotspots? 200mb of (plain?) code
seems to be good material for this.
---
Grigory Zagorodnev
Intel Corporation
>-----Original Message-----
>From: binutils-owner@sources.redhat.com [mailto:binutils-
>owner@sources.redhat.com] On Behalf Of Stas Kiselev
>Sent: Monday, April 04, 2005 6:52 PM
>To: binutils@sources.redhat.com
>Subject: GAS
>
>Hello,
>
> I use AS for generating object files where time is
>critical.
>I mean I have to speed up gas as much as possible. As for
>input I give AS
>very big .asm files with size more than 200mb. so it works
>very slow. I
>tried to cut input file to several small .asm files - AS
>became work more
>faster but in general AS work very slow. How can I speed up
>it ? What kind
>of weak points can I find and fix ?
>
>P.S. Where can I get whole description of AS architecture?
>for instance I have
>descriptinon for lcc compilator - "A retargetable C
>compiler: design and implementation"
>
>Thank you, Stanislav
next reply other threads:[~2005-04-04 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 16:03 Zagorodnev, Grigory [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 9:11 Re[2]: GAS Stas Kiselev
2005-04-15 10:48 ` GAS Nick Clifton
2005-04-12 13:53 GAS Zagorodnev, Grigory
2005-04-14 9:00 ` GAS Nick Clifton
2005-04-05 7:52 Re[2]: GAS Zagorodnev, Grigory
2005-04-06 11:17 ` GAS Nick Clifton
2005-04-04 14:51 GAS Stas Kiselev
2004-05-05 14:09 GAS Arun Vishwanathan
2004-05-05 13:49 GAS Bill Cunningham
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=F92C2EFE7C3BA745855BF7036E1F3F9AADBF10@NNSMSX401 \
--to=grigory.zagorodnev@intel.com \
--cc=binutils@sources.redhat.com \
--cc=stas_kiselev@bk.ru \
/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).