public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	 "leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
	"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [PATCH] BaseTools/Scripts: discard .gnu.hash section in GCC builds
Date: Sun, 28 May 2017 12:08:15 +0000	[thread overview]
Message-ID: <CAKv+Gu9_ugXMBjpDurNPjNMxvm0szrgdTmO++nyemBjuu5GGRQ@mail.gmail.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14D740305@shsmsx102.ccr.corp.intel.com>

On 27 May 2017 at 09:05, Gao, Liming <liming.gao@intel.com> wrote:
> Ard:
>   I just run BaseTools\Scripts\PatchCheck.py to check the latest patches. It reports one issue in this patch. Could you fix it?
>

Pushed as f4d3ba87bb8f

-- 
Ard.

> The commit message format passed all checks.
> Code format is not valid:
>  * Line ending ('\n') is not CRLF
>    File: BaseTools/Scripts/GccBase.lds
>    Line:     *(.hash .gnu.hash)
>
> Thanks
> Liming
>> -----Original Message-----
>> From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
>> Sent: Wednesday, May 24, 2017 9:13 PM
>> To: Gao, Liming <liming.gao@intel.com>
>> Cc: edk2-devel@lists.01.org; leif.lindholm@linaro.org; Zhu, Yonghong <yonghong.zhu@intel.com>
>> Subject: Re: [PATCH] BaseTools/Scripts: discard .gnu.hash section in GCC builds
>>
>> On 21 May 2017 at 21:05, Gao, Liming <liming.gao@intel.com> wrote:
>> > Reviewed-by: Liming Gao <liming.gao@intel.com>
>> >
>>
>> Thanks. Pushed as 00b00cc57bfe0fca54c904d4dd44a263e243c88b
>>
>> >>-----Original Message-----
>> >>From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
>> >>Sent: Friday, May 19, 2017 6:48 PM
>> >>To: edk2-devel@lists.01.org
>> >>Cc: leif.lindholm@linaro.org; Zhu, Yonghong <yonghong.zhu@intel.com>; Gao,
>> >>Liming <liming.gao@intel.com>; Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> >>Subject: [PATCH] BaseTools/Scripts: discard .gnu.hash section in GCC builds
>> >>
>> >>Some builds of GCC/binutils will default to using the GNU flavor of
>> >>the symbol hash table, and will emit it into a section called .gnu.hash
>> >>rather than .hash. We have no use for its contents, and GenFw ignores
>> >>it anyway, so it shouldn't really matter what we do with it.
>> >>
>> >>However, due to a workaround for AARCH64 we have in GenFw to deal with
>> >>older GCCs that corrupt section-based relocations when merging sections
>> >>during the final link, we need the ELF and PE/COFF views of the binary
>> >>to be identical. Since we don't place the .gnu.hash section explicitly,
>> >>it may end up at the beginning of the ELF binary, causing other sections
>> >>to be shifted in the ELF view but not in the PE/COFF view.
>> >>
>> >>So let's add .gnu.hash to the GCC linker script. We don't care about its
>> >>contents so add it to the /DISCARD/ section.
>> >>
>> >>Contributed-under: TianoCore Contribution Agreement 1.0
>> >>Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> >>---
>> >> BaseTools/Scripts/GccBase.lds | 2 +-
>> >> 1 file changed, 1 insertion(+), 1 deletion(-)
>> >>
>> >>diff --git a/BaseTools/Scripts/GccBase.lds b/BaseTools/Scripts/GccBase.lds
>> >>index 41e5c0b4a769..a43e0072f2b4 100644
>> >>--- a/BaseTools/Scripts/GccBase.lds
>> >>+++ b/BaseTools/Scripts/GccBase.lds
>> >>@@ -78,7 +78,7 @@ SECTIONS {
>> >>     *(.dynsym)
>> >>     *(.dynstr)
>> >>     *(.dynamic)
>> >>-    *(.hash)
>> >>+    *(.hash .gnu.hash)
>> >>     *(.comment)
>> >>     *(COMMON)
>> >>   }
>> >>--
>> >>2.9.3
>> >


      reply	other threads:[~2017-05-28 12:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 10:47 [PATCH] BaseTools/Scripts: discard .gnu.hash section in GCC builds Ard Biesheuvel
2017-05-19 10:58 ` Leif Lindholm
2017-05-22  4:05 ` Gao, Liming
2017-05-24 13:13   ` Ard Biesheuvel
2017-05-27  9:05     ` Gao, Liming
2017-05-28 12:08       ` Ard Biesheuvel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKv+Gu9_ugXMBjpDurNPjNMxvm0szrgdTmO++nyemBjuu5GGRQ@mail.gmail.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox