public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Aaron W. LaFramboise" <aaron98wiridge9@aaronwl.com>
To: Dmitriy Nikitinskiy <nick@bel.ru>
Cc: binutils@sources.redhat.com
Subject: Re: LD improvements on PE (mingw)
Date: Wed, 01 Jun 2005 14:21:00 -0000	[thread overview]
Message-ID: <429DC43E.9050700@aaronwl.com> (raw)
In-Reply-To: <429D96DA.6060107@bel.ru>

Dmitriy Nikitinskiy wrote:

> I have strange situation on linking for PE under win32 and linux.
> When I run link under win32, they work about 8 min and uses more than
> 200 Mb RAM.

This seems pretty significant to me.  First, make sure there aren't any
external factors such as libtool that might be slowing this down.

> Why equal versions (GNU ld version 2.13.90 20030111) of binutils give
> too different results?

If you're interested in investigating this, I might recommend building a
crosscompiler to another COFF target, such as i386-coff, to get a better
performance comparison.  It would be good to know if the problem was
PECOFF-specific, or more generally COFF-specific.

Beyond this, the thing to do here is to build all of these
crosscompilers with profiling enabled.  gprof is the way to go here,
unless you have something better.  Since the performance difference is
so significant, profiling may be very helpful.

> Does any body works at this time to improve performance of linking for
> PE under win32?

I don't know, but there are a few people interested in making
performance improvements to binutils in general.  Most people are
interested in ELF targets, though.


Aaron W. LaFramboise

      reply	other threads:[~2005-06-01 14:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 11:05 Dmitriy Nikitinskiy
2005-06-01 14:21 ` Aaron W. LaFramboise [this message]

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=429DC43E.9050700@aaronwl.com \
    --to=aaron98wiridge9@aaronwl.com \
    --cc=binutils@sources.redhat.com \
    --cc=nick@bel.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).