From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.224.172.66 with SMTP id k2mr11838678qaz.4.1372696501511; Mon, 01 Jul 2013 09:35:01 -0700 (PDT) X-Received: by 10.49.40.167 with SMTP id y7mr727078qek.36.1372696501495; Mon, 01 Jul 2013 09:35:01 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!mx05.eternal-september.org!feeder.eternal-september.org!news.bbs-scene.org!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!y2no9279qax.0!news-out.google.com!f7ni507qai.0!nntp.google.com!y2no9278qax.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Mon, 1 Jul 2013 09:35:01 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=189.77.226.1; posting-account=TRgI1QoAAABSsYi-ox3Pi6N-JEKKU0cu NNTP-Posting-Host: 189.77.226.1 References: <9cbe0ad4-f54c-4c99-ba58-4db027ae962e@googlegroups.com> <70b1d2b0-d5ab-431e-84b9-9f00af08dbe2@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <91dea591-19d5-484d-a13d-db86bbf0b3b8@googlegroups.com> Subject: Re: Size optimization for objects From: "Rego, P." Injection-Date: Mon, 01 Jul 2013 16:35:01 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: news.eternal-september.org comp.lang.ada:16018 Date: 2013-07-01T09:35:01-07:00 List-Id: On Monday, July 1, 2013 12:28:24 PM UTC-3, Niklas Holsti wrote: > In the linker world, "symbol value" usually means the address of the > object or subprogram identified by the symbol. However, sometimes > symbols can also stand for other kinds of values (offsets or sizes), but > that is less common. Ok, now I understand. Thanks. > My "nm", on my 64-bit system, generates the value/address as a single > column with 16-digit hex values, followed by "D" and other codes in the > second column. Perhaps your "nm" separates the 16 hex digits into two > 8-digit groups, for easier reading? Are you using 32-bit or 64-bit binaries? I am using 32-bit binaries. Actually, it generates 2 columns of 8 hex digits only when I put the options --print-sizes --size-sort. Otherwise, it gives me something like 02d62538 N .stab When I put the option --print-size --size-sort, it gives me (in a big list) 02d62538 fd3c61e0 N .stab so I wonder that the second column should be the size. However, if I add all those second columns, the sum result is incoherent (much much bigger) with the real size of the final binary. Maybe is it masked with something I am missing? > > > > > Also, the second column represents the symbol size (in bytes I > > > presume). > > > > From your example, I doubt that: ff42d001 does not seem a likely size > > for anything. > > > > -- > > Niklas Holsti > > Tidorum Ltd > > niklas holsti tidorum fi > > . @ .