public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Matt Rice <ratmice@gmail.com>
To: archer@sourceware.org, Yao Qi <qiyaoltc@gmail.com>
Subject: Re: C++ draft
Date: Tue, 28 Jun 2011 17:08:00 -0000	[thread overview]
Message-ID: <BANLkTimEgdKFh+erCZ_5CO2j2Zao-x7RZw@mail.gmail.com> (raw)
In-Reply-To: <20110628122135.GB3005@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2274 bytes --]

On Tue, Jun 28, 2011 at 5:21 AM, Gary Benson <gbenson@redhat.com> wrote:

> The resulting executable is slightly larger (6562 bytes from 6433).

note that these numbers are equivalent to the hello-c++1 from the
attached foo.sh shell script, which brings in a bunch of shared
libraries.  I tried some other sources/linking scenerios to get an
idea of the footprint. (below is the output).

of concern is that of the *-tdep.c files:
amd64, i386, ppc, rs6000, and spu, (at least) use TRY_CATCH or throw_*

and that at least arm uses VEC

I'm not sure how far outside of *-tdep.c this stuff would propagate.


here is the output:
File: hello-c
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
File: hello-c++1
 0x0000000000000001 (NEEDED)             Shared library: [libstdc++.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libgcc_s.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
File: hello-c++2
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
File: hello-c++3
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
File: hello-exceptions
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [ld-linux-x86-64.so.2]
File: hello-exceptions+vector
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [ld-linux-x86-64.so.2]
File: hello-vector
 0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
 0x0000000000000001 (NEEDED)             Shared library: [ld-linux-x86-64.so.2]
6.3K	./hello-c
6.5K	./hello-c++1
6.3K	./hello-c++2
6.4K	./hello-c++3
106K	./hello-exceptions
166K	./hello-exceptions+vector
156K	./hello-vector
stripped
4.2K	./hello-c
4.3K	./hello-c++1
4.2K	./hello-c++2
4.3K	./hello-c++3
86K	./hello-exceptions
122K	./hello-exceptions+vector
118K	./hello-vector

[-- Attachment #2: foo.sh --]
[-- Type: application/x-sh, Size: 1511 bytes --]

  reply	other threads:[~2011-06-28 17:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27 21:08 Tom Tromey
2011-06-27 21:23 ` [Archer] " Joel Brobecker
2011-06-29 19:55   ` Tom Tromey
2011-06-29 21:47     ` [Archer] " Joel Brobecker
2011-06-28  4:33 ` Matt Rice
2011-06-28  8:21 ` Yao Qi
2011-06-28 12:21   ` Gary Benson
2011-06-28 17:08     ` Matt Rice [this message]
2011-06-28 17:36     ` Jan Kratochvil
2011-06-29 20:08     ` Tom Tromey
2011-06-29 20:06   ` Tom Tromey
2011-06-30  6:06     ` Yao Qi
2011-09-26 21:01       ` Jim Blandy
2011-06-29 18:52 ` Stan Shebs
2011-06-29 19:03   ` [Archer] " Joel Brobecker

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=BANLkTimEgdKFh+erCZ_5CO2j2Zao-x7RZw@mail.gmail.com \
    --to=ratmice@gmail.com \
    --cc=archer@sourceware.org \
    --cc=qiyaoltc@gmail.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).