Re: Size optimization for objects

[Niklas Holsti <niklas.holsti@tidorum.invalid>]

On 13-07-01 17:35 , Rego, P. wrote:

> I am still having some difficult in understand the information
> generated by nm. It generates something like
> 00c038d6 ff42d001 D ___gl_locking_policy
> 
> The first column I think it's the "symbol value", the second column I
> guess it's the size of the symbol. The other columns are ok, since
> the man nm explains quite well. What does "symbol value" mean?

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.

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?

> 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
      .      @       .