From: Fco Javier <jabarca@ya.com>
To: gcc-help@gcc.gnu.org
Subject: Work around too long C++ symbol names
Date: Wed, 25 Feb 2004 11:18:00 -0000 [thread overview]
Message-ID: <403C8374.3030104@ya.com> (raw)
Hello,
I saw the "How to work around too long C++ symbol names (-fsquangle)"
FAQ of G++ and i have a question about this:
I am interested in reducig my G++ executable file size in a linux ARM
based device. At the moment my executable has 700kBytes around and
gziped the file is reduced to 200Kbytes of size. I thik this amount of
size is due to g++ name mangling I used the nm utility and saw the
generated names to the methods of clasess and these are preceded of
class name. This is very expensive in the final executable file size.
1) I don't know what makes -fsquangle option with then symbol names. Is
there any documentation about this?
2) It is possible to "obfuscate" some symbolnames in the final
executable file to reduce the file size of may executable. In the faq is
metioned the use of GNU as. Where can find some documentation or
dicussion groups about this?
Thank you very much
Best regards,
Javier
next reply other threads:[~2004-02-25 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 11:18 Fco Javier [this message]
2004-02-25 12:55 ` Ken Foskey
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=403C8374.3030104@ya.com \
--to=jabarca@ya.com \
--cc=gcc-help@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).