public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Karl M. Hegbloom" <hegbloom@pdx.edu>
To: gcc-bugs@gcc.gnu.org
Subject: Coalesce object-code identical dtor, template, etc. ?
Date: Tue, 03 Jun 2003 18:49:00 -0000	[thread overview]
Message-ID: <1054666134.2611.7.camel@bittersweet.hegbloom.net> (raw)

When I use a template instantiated with a pointer to type, or when more
than one automaticly generated function is created...  The object code I
see when I compile it with "-S" often has several functions in it that
are _identical_, instruction for instruction, other than their jump
label, which only "really" exists in the compiler/assembler, not at
runtime.  I think that a good optimization would be to detect that, and
just write two labels and one function.  This will reduce the object
binary size, perhaps considerably.  Also, can the linker do this as
well?

Q: Are there pre-compiled STL data types instantiated with
pointer-to-type that could be reused in the above fashion?

-- 
Karl M. Hegbloom <hegbloom@pdx.edu>


                 reply	other threads:[~2003-06-03 18:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1054666134.2611.7.camel@bittersweet.hegbloom.net \
    --to=hegbloom@pdx.edu \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).