This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [gold] alignment of static globals
- From: Christopher Jelesnianski <bielsk1 at vt dot edu>
- To: Alan Modra <amodra at gmail dot com>
- Cc: Binutils <binutils at sourceware dot org>
- Date: Wed, 25 May 2016 11:20:15 -0400
- Subject: Re: [gold] alignment of static globals
- Authentication-results: sourceware.org; auth=none
- References: <CAH=yU0ajGAwV3rEviBHEFktYRKMLeCXKC1V0ONZi0++gv1-37w at mail dot gmail dot com> <20160525003539 dot GH3300 at bubble dot grove dot modra dot org>
I guess I should add I am using the following as my CFLAGS:
CFLAGS := -O3 -Wall -g -gdwarf-aranges -c -DPOSIX -fopenmp=libomp
HET_CFLAGS := $(CFLAGS) -nostdinc -ffunction-sections -fdata-sections
-fno-common -ftls-model=initial-exec
I am already using -fno-common. It doesn't seem to apply to
uninitialized static globals that are in the .bss section for some
reason
On Tue, May 24, 2016 at 8:35 PM, Alan Modra <amodra@gmail.com> wrote:
> On Tue, May 24, 2016 at 06:28:55PM -0400, Christopher Jelesnianski wrote:
>> How can I enforce static uninitialized global variables to follow my
>> linker script (without just removing the static keyword)?? Can such
>
> Compile with -fno-common.
>
> --
> Alan Modra
> Australia Development Lab, IBM