From: Daniel Jacobowitz <drow@false.org>
To: Chris Kirby <ckirby@laurelnetworks.com>
Cc: Alan Modra <amodra@bigpond.net.au>, binutils@sources.redhat.com
Subject: Re: Changing .dynstr to be more C++ friendly?
Date: Thu, 24 Feb 2005 17:28:00 -0000 [thread overview]
Message-ID: <20050224161124.GA31283@nevyn.them.org> (raw)
In-Reply-To: <5.1.0.14.0.20050224093737.01cf16a0@sherlock>
On Thu, Feb 24, 2005 at 09:52:12AM -0500, Chris Kirby wrote:
> At 12:17 PM 2/24/2005 +1030, Alan Modra wrote:
> >On Wed, Feb 23, 2005 at 02:22:50PM -0500, Chris Kirby wrote:
> >> My thinking was that we could change the definition of an Elf symbol
> >> to not contain a single name, but rather N distinct name components
> >> (3 in this case).
> >
> >I think you underestimate the scope of the change you are proposing.
> >This would require changes to all consumers of ELF files, which means
> >more than just the assembler and linker. Debuggers, ld.so, etc.
>
> I was hoping that they all used bfd or liberty so we would only have
> to change it there. If everyone has there own code to interact with
> ELF files, then I agree it would be too large of a change to be
> feasible right now. If ELF is ever revised, it would be nice to
> consider ways to compress the dynamic strings for languages other
> than just C.
>
> For our embedded application, I am wondering how feasible it would be
> to change the symbol names to something shorter. As long as the
> application and the shared library are in agreement in what the
> symbol names are, it should not matter what they are. This would
> allow us to come up with a more compact naming scheme than the
> current C++ name mangler. I could imagine a post processing step
> after the application and libraries are built where the current names
> in use are found, converted to a shorter representation, and then
> replaced.
I don't know if this will interfere with any of the C++ support library
functions, but you can probably make it work. It's not hard to rename
symbols in an ELF file.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-02-24 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 1:11 Chris Kirby
2005-02-24 13:15 ` MIPS gas doesn't set SH_FLAG Brett Porter
2005-02-28 19:38 ` Nick Clifton
2005-03-01 1:18 ` Eric Christopher
2005-03-01 9:47 ` Nick Clifton
2005-03-01 16:38 ` Brett Porter
2005-03-01 17:27 ` Eric Christopher
2005-02-24 13:58 ` Changing .dynstr to be more C++ friendly? Alan Modra
2005-02-24 17:14 ` Chris Kirby
2005-02-24 17:28 ` Daniel Jacobowitz [this message]
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=20050224161124.GA31283@nevyn.them.org \
--to=drow@false.org \
--cc=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=ckirby@laurelnetworks.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).