From: Jim Wilson <wilson@tuliptree.org>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: Andi Kleen <ak@suse.de>, Andreas Schwab <schwab@suse.de>,
gcc@gcc.gnu.org, nabeel@netzero.com
Subject: Re: Huge Increase in Unstripped Executable Size G++ 2.95 to 3.2
Date: Sat, 01 Mar 2003 03:54:00 -0000 [thread overview]
Message-ID: <1046490897.1001.8.camel@leaf.tuliptree.org> (raw)
In-Reply-To: <3E5FBCEF.7050203@moene.indiv.nluug.nl>
On Fri, 2003-02-28 at 14:47, Toon Moene wrote:
> How would your scheme work in this case ?
It isn't my scheme. I don't know the details of how it works.
If you are using static libraries (archives), then I think it would work
fine, since the archives just contain the object files with the original
debug info.
Shared libraries are a different matter. The debug info would have to
be in the shared library, or you would have to keep the original
objects. Either way there doesn't seem to be much benefit here for
shared libraries.
Jim
WARNING: multiple messages have this Message-ID
From: Jim Wilson <wilson@tuliptree.org>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: Andi Kleen <ak@suse.de>, Andreas Schwab <schwab@suse.de>,
gcc@gcc.gnu.org, nabeel@netzero.com
Subject: Re: Huge Increase in Unstripped Executable Size G++ 2.95 to 3.2
Date: Sun, 02 Mar 2003 21:26:00 -0000 [thread overview]
Message-ID: <1046490897.1001.8.camel@leaf.tuliptree.org> (raw)
Message-ID: <20030302212600.8zBQM9BrmSahN7xrXTZoHqEcn4VyrJfgYRTHj0_OLhs@z> (raw)
In-Reply-To: <3E5FBCEF.7050203@moene.indiv.nluug.nl>
On Fri, 2003-02-28 at 14:47, Toon Moene wrote:
> How would your scheme work in this case ?
It isn't my scheme. I don't know the details of how it works.
If you are using static libraries (archives), then I think it would work
fine, since the archives just contain the object files with the original
debug info.
Shared libraries are a different matter. The debug info would have to
be in the shared library, or you would have to keep the original
objects. Either way there doesn't seem to be much benefit here for
shared libraries.
Jim
next prev parent reply other threads:[~2003-03-01 3:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030227.154544.18888.253032@webmail06.lax.untd.com.suse.lists.egcs>
[not found] ` <3E5ED96F.9090902@tuliptree.org.suse.lists.egcs>
2003-02-28 10:29 ` Andi Kleen
2003-02-28 13:25 ` Andreas Schwab
2003-02-28 14:00 ` Andi Kleen
2003-02-28 14:25 ` Daniel Berlin
2003-02-28 15:43 ` Daniel Jacobowitz
2003-02-28 16:57 ` Andi Kleen
2003-02-28 18:25 ` Jim Wilson
2003-02-28 19:35 ` Devang Patel
2003-02-28 21:01 ` Toon Moene
2003-03-01 3:54 ` Jim Wilson [this message]
2003-03-02 21:26 ` Jim Wilson
2003-03-03 10:25 ` Alexandre Oliva
2003-02-28 19:53 ` Devang Patel
2003-02-28 19:54 ` Devang Patel
2003-02-28 17:29 ` Jim Wilson
2003-03-01 13:23 ` Michael S. Zick
2003-03-01 16:12 ` Daniel Jacobowitz
2003-02-28 19:03 Benjamin Kosnik
2003-02-28 23:25 ` snyder
2003-02-28 23:26 ` Richard Henderson
2003-02-28 23:28 ` Daniel Jacobowitz
2003-03-01 1:21 ` Richard Henderson
2003-03-01 18:35 ` Andi Kleen
2003-02-28 23:48 ` Mike Stump
2003-03-01 1:38 ` Mark Mitchell
2003-03-01 2:05 ` Richard Henderson
2003-03-01 4:36 ` Devang Patel
2003-03-01 4:52 ` Devang Patel
2003-03-03 6:56 ` Mark Mitchell
2003-03-03 7:01 ` Neil Booth
2003-03-03 8:58 ` Gabriel Dos Reis
2003-03-03 18:25 ` Richard Henderson
2003-03-01 14:52 ` Jason Molenda
2003-03-01 18:56 ` Jason Molenda
-- strict thread matches above, loose matches on Subject: below --
2003-02-28 14:16 Robert Dewar
2003-02-28 1:38 nabeel
2003-02-28 3:15 ` Daniel Jacobowitz
2003-02-28 6:29 ` Jim Wilson
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=1046490897.1001.8.camel@leaf.tuliptree.org \
--to=wilson@tuliptree.org \
--cc=ak@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=nabeel@netzero.com \
--cc=schwab@suse.de \
--cc=toon@moene.indiv.nluug.nl \
/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).