This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: How to guarantee alignment for .comm and .lcomm defined variables

From: Alan Modra <amodra at bigpond dot net dot au>
To: Mayank Kumar <mayank at microsoft dot com>
Cc: "binutils at sourceware dot org" <binutils at sourceware dot org>
Date: Tue, 24 Apr 2007 23:11:06 +0930
Subject: Re: How to guarantee alignment for .comm and .lcomm defined variables
References: <76EBE649FB0E0E4DA883B5840459059F1445C770D5@AA-EXMSG-C412.southpacific.corp.microsoft.com> <20070422235501.GA10537@bubble.grove.modra.org> <76EBE649FB0E0E4DA883B5840459059F144F29264F@AA-EXMSG-C412.southpacific.corp.microsoft.com> <76EBE649FB0E0E4DA883B5840459059F144F2926F9@AA-EXMSG-C412.southpacific.corp.microsoft.com>

.lcomm doesn't really create common symbols.  Instead you get a local
symbol in .bss that isn't any different from a local symbol allocated
in say, .data.  Allocation and alignment is done by the assembler.
Common symbols on the other hand are allocated (or merged with a
normal symbol) by the linker.  ELF common symbols have both size and
alignment.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

References:
- Issues with gcc Assembler on Interix when generating PIC code
  - From: Mayank Kumar
- Re: Issues with gcc Assembler on Interix when generating PIC code
  - From: Alan Modra
- RE: Issues with gcc Assembler on Interix when generating PIC code
  - From: Mayank Kumar
- How to guarantee alignment for .comm and .lcomm defined variables
  - From: Mayank Kumar

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]