public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
To: mrs@wrs.com
Cc: carlo@runaway.xs4all.nl, egcs@cygnus.com
Subject: Re: #pragma interface && generating virtual tables (of templates?)
Date: Mon, 22 Feb 1999 15:52:00 -0000	[thread overview]
Message-ID: <199902222349.AAA00707@mira.isdn.cs.tu-berlin.de> (raw)
In-Reply-To: < 199902222130.NAA00669@kankakee.wrs.com > (mrs@wrs.com)

> > With #pragma       86 s                 1649639 bytes
> > Without #pragma    86 s                 1663340 bytes
> 
> Thanks for the information.  It'd be nice to track down these random
> few bytes that were not squeezed out

One source certainly is garbage exception regions. If we have linkonce
functions, they get slots in .gcc_except_table, and .eh_frame. Once
duplicate code is removed, the duplicate slots stay. I don't know
whether this would accound for the 14K; having a section-by-section
comparison would be helpful.

Regards,
Martin

WARNING: multiple messages have this Message-ID
From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
To: mrs@wrs.com
Cc: carlo@runaway.xs4all.nl, egcs@cygnus.com
Subject: Re: #pragma interface && generating virtual tables (of templates?)
Date: Sun, 28 Feb 1999 22:53:00 -0000	[thread overview]
Message-ID: <199902222349.AAA00707@mira.isdn.cs.tu-berlin.de> (raw)
Message-ID: <19990228225300.OZ0DcbP_2Gk77uhhig0S6gpGk6KHLmwMKN7ix8Jk0Aw@z> (raw)
In-Reply-To: <199902222130.NAA00669@kankakee.wrs.com>

> > With #pragma       86 s                 1649639 bytes
> > Without #pragma    86 s                 1663340 bytes
> 
> Thanks for the information.  It'd be nice to track down these random
> few bytes that were not squeezed out

One source certainly is garbage exception regions. If we have linkonce
functions, they get slots in .gcc_except_table, and .eh_frame. Once
duplicate code is removed, the duplicate slots stay. I don't know
whether this would accound for the 14K; having a section-by-section
comparison would be helpful.

Regards,
Martin

  parent reply	other threads:[~1999-02-22 15:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-22 13:30 Mike Stump
     [not found] ` < 199902222130.NAA00669@kankakee.wrs.com >
1999-02-22 15:52   ` Martin v. Loewis [this message]
     [not found]     ` < 199902222349.AAA00707@mira.isdn.cs.tu-berlin.de >
1999-02-23  9:18       ` #pragma interface Carlo Wood
1999-02-28 22:53         ` Carlo Wood
1999-02-28 22:53     ` #pragma interface && generating virtual tables (of templates?) Martin v. Loewis
1999-02-28 22:53 ` Mike Stump
  -- strict thread matches above, loose matches on Subject: below --
1999-02-20 10:38 Carlo Wood
     [not found] ` < 199902201741.SAA11876@jolan.ppro >
1999-02-20 11:35   ` Martin v. Loewis
     [not found]     ` < 199902201932.UAA03305@mira.isdn.cs.tu-berlin.de >
1999-02-20 20:38       ` Carlo Wood
1999-02-28 22:53         ` Carlo Wood
1999-02-28 22:53     ` Martin v. Loewis
1999-02-28 22:53 ` Carlo Wood

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=199902222349.AAA00707@mira.isdn.cs.tu-berlin.de \
    --to=martin@mira.isdn.cs.tu-berlin.de \
    --cc=carlo@runaway.xs4all.nl \
    --cc=egcs@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).