This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [GOLD][PATCH] Set SHF_LINK_ORDER flags of ARM EXIDX sections.
- From: Ian Lance Taylor <iant at google dot com>
- To: Doug Kwan (éæå) <dougkwan at google dot com>
- Cc: binutils <binutils at sourceware dot org>
- Date: Tue, 19 Oct 2010 07:07:56 -0700
- Subject: Re: [GOLD][PATCH] Set SHF_LINK_ORDER flags of ARM EXIDX sections.
- References: <AANLkTik85+uiwZ8K4Yo236CnfpnYY6UhX3FzD-CKQgXr@mail.gmail.com>
"Doug Kwan (éæå)" <dougkwan@google.com> writes:
> This patch changes code writing output section headers so that the
> SHF_LINK_ORDER flag of a section of type SHT_ARM_EXIDX is always set.
> The flag is required to be set for such a section by the ARM EHABI.
> The existing code drops the SHF_LINK_ORDER flag and that confuses
> other tools. Gold does not handle SHF_LINK_ORDER in general but the
> ARM back-end can handle the EXIDX sections.
>
> -Doug
>
>
> 2010-10-19 Doug Kwan <dougkwan@google.com>
>
> * output.cc(Output_section::write_header): Set SHF_LINK_ORDER flags of
> ARM EXIDX sections.
I don't see the ARM backend actually creating any SHT_ARM_EXIDX
sections. So it seems to me that they are input sections. If the ABI
requires the input sections to have the SHF_LINK_ORDER flag set, then
that setting should carry through to the output section. Does that not
happen?
Ian