From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] CONFIG_REMAKE_ELF for aarch64
Date: Wed, 2 Apr 2014 09:15:31 -0700 [thread overview]
Message-ID: <533C37A3.7060603@freescale.com> (raw)
In-Reply-To: <cd68608.cfc3.14521eae07d.Coremail.fenghua@phytium.com.cn>
On 04/02/2014 03:10 AM, FengHua wrote:
>
>> -----Original Messages-----
>> From: "York Sun" <yorksun@freescale.com>
>> Sent Time: 2014-03-22 02:10:39 (Saturday)
>> To: "Scott Wood" <scottwood@freescale.com>
>> Cc: FengHua <fenghua@phytium.com.cn>, "u-boot at lists.denx.de" <u-boot@lists.denx.de>
>> Subject: CONFIG_REMAKE_ELF for aarch64
>>
>> Scott,
>>
>> I am having a problem recreating u-boot.elf for aarch64 targets. The file is OK
>> when Ttext is aligned with 64KB boundary, for example 0x30000000. But if I use
>> 0x30001000 as the text base, the result u-boot.elf has additional offset of
>> 0x10000. For example, the first instruction should be (from objdump)
>>
>> 30001000: 1400000a b 30001028
>>
>> But it is
>>
>> 30011000: 1400000a b 30011028
>>
>> My gcc version is
>>
>> gcc version 4.8.3 20131202 (prerelease) (crosstool-NG linaro-1.13.1-4.8-2013.12
>> - Linaro GCC 2013.11)
>>
>> GNU ld (crosstool-NG linaro-1.13.1-4.8-2013.12 - Linaro GCC 2013.11) 2.24.0.20131220
>> Supported emulations:
>> aarch64linux
>> aarch64elf
>> aarch64elf32
>> aarch64elf32b
>> aarch64elfb
>> armelf
>> armelfb
>> aarch64linuxb
>> aarch64linux32
>> aarch64linux32b
>> armelfb_linux_eabi
>> armelf_linux_eabi
>>
>> I am hoping you or someone familiar with ABI or something related and shed some
>> light.
>>
>> York
> Maybe this is a bug of aarch64 tool chain.
>
>
Scott suspects it is an alignment issue with the toolchain. But we didn't get
the bottom of it.
York
prev parent reply other threads:[~2014-04-02 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 18:10 [U-Boot] CONFIG_REMAKE_ELF for aarch64 York Sun
2014-04-02 10:10 ` FengHua
2014-04-02 16:15 ` York Sun [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-all 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=533C37A3.7060603@freescale.com \
--to=yorksun@freescale.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.