Incorrect Listing Output with .lcomm

Incorrect Listing Output with .lcomm

[Tracy Kuhrt]

Given the source:
        .data

        .lcomm a, 1

        .lcomm b, 50
        .lcomm c, 1

        .text
foo:
        .lcomm d, 1
        .lcomm e, 10
        .lcomm f, 20
        .lcomm g, 1
        .end


binutils configured for a target of sparc-sun-coff generates the
following listing file in which the line numbers listed under DEFINED
SYMBOLS do not match the line numbers where the symbol was defined.
Also, the very first symbol 'a', does not have an associated file and
line number.

Any ideas where I should start looking?

SPARC GAS  /home/users/kuhrtt/tmp/lcomm.s                       page 1


   1                            .data
   2
   3                            .lcomm a, 1
   4
   5                            .lcomm b, 50
   6                            .lcomm c, 1
   7
   8                            .text
   9                    foo:
  10                            .lcomm d, 1
  11                            .lcomm e, 10
  12                            .lcomm f, 20
  13                            .lcomm g, 1
  14                            .end

SPARC GAS  /home/users/kuhrtt/tmp/lcomm.s                       page 2


DEFINED SYMBOLS
                            *ABS*:00000000 fake
                             .bss:00000000 a
/home/users/kuhrtt/tmp/lcomm.s:5      .bss:00000008 b
/home/users/kuhrtt/tmp/lcomm.s:5      .bss:0000003a c
/home/users/kuhrtt/tmp/lcomm.s:9      .text:00000000 foo
/home/users/kuhrtt/tmp/lcomm.s:6      .bss:0000003b d
/home/users/kuhrtt/tmp/lcomm.s:11     .bss:00000040 e
/home/users/kuhrtt/tmp/lcomm.s:12     .bss:00000050 f
/home/users/kuhrtt/tmp/lcomm.s:12     .bss:00000064 g
                            .text:00000000 .text
                            .data:00000000 .data
                             .bss:00000000 .bss

NO UNDEFINED SYMBOLS

Re: Incorrect Listing Output with .lcomm

[Nick Clifton]

Hi Tracy,

> binutils configured for a target of sparc-sun-coff generates the
> following listing file in which the line numbers listed under DEFINED
> SYMBOLS do not match the line numbers where the symbol was defined.
> Also, the very first symbol 'a', does not have an associated file and
> line number.
> 
> Any ideas where I should start looking?

I suggest you start by examining the code in s_lcomm_internal() in
gas/read.c.  This parses the .lcomm directive and assigns a frag to
the newly creqted symbol, and it is the frag that contains the line
number information.

Cheers
        Nick