From: Joe Buck <jbuck@synopsys.com>
To: mrs@wrs.com (Mike Stump)
Cc: jason@cygnus.com, jbuck@synopsys.com, egcs@cygnus.com
Subject: Re: collect2 always built?
Date: Tue, 03 Feb 1998 12:11:00 -0000 [thread overview]
Message-ID: <199802032010.MAA09583@atrus.synopsys.com> (raw)
In-Reply-To: <199802031959.LAA17446@kankakee.wrs.com>
> > If someone has ELF and the latest GNU ld, is there ever a situation where
> > they would want to use -frepo?
>
> I think so. Speed. I predict that there are cases where using -frepo
> will yield smaller .o files, and will take less time to generate them
> and less time to link them.
I would be amazed. My experience with -frepo is that it is dog-slow, and
with 2.7.2 I saw as many as ten link-recompile passes on relatively small
programs that used STL. This should be better (fewer passes) with egcs
because templates are inlined more readily, but where templates call other
templates the work can be considerable.
> Though I admit I have never benchmarked it.
That is quite apparent.
> Also, this is probably
> only an issue for large projects (it takes an hour to link, type
> ones).
There are other problems with -frepo for large projects, having to do with
library reuse.
next prev parent reply other threads:[~1998-02-03 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-03 11:59 Mike Stump
1998-02-03 12:11 ` Joe Buck [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-02-03 18:37 Mike Stump
1998-02-03 14:34 Mike Stump
1998-02-03 23:22 ` Mike Simons
1998-02-02 10:32 Todd Vierling
1998-02-02 11:14 ` Jeffrey A Law
1998-02-02 11:14 ` Joe Buck
1998-02-02 11:43 ` Mumit Khan
[not found] ` <29942.886446984.cygnus.egcs@hurl.cygnus.com>
1998-02-03 0:40 ` Jason Merrill
1998-02-03 9:54 ` Joe Buck
1998-02-03 11:59 ` Alexandre Oliva
1998-02-03 11:59 ` Mumit Khan
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=199802032010.MAA09583@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.com \
--cc=mrs@wrs.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).