From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V3 RESEND 0/5] Add ILP32 support in aarch64
Date: Tue, 2 Feb 2016 12:16:24 +0100 [thread overview]
Message-ID: <56B09008.8030202@mind.be> (raw)
In-Reply-To: <56B089D6.4070106@huawei.com>
On 02-02-16 11:49, Zhangjian (Bamvor) wrote:
> Hi, Romain
>
> On 2016/2/2 17:04, Romain Naour wrote:
>> Hi Bamvor,
>>
>> Le 02/02/2016 03:29, Zhangjian (Bamvor) a ?crit :
[snip]
>>> You could this glibc[1]. IIRC, It is for patch v6 rfc2. We are planning to
>>> update it for patch v6 rfc5.
>>
>> Thanks for this link.
>>
>> To be honest, I don't think this series will be merged as is until a stable
>> toolchain release is made.
> What's your mean stable toolchain? A toolchain release from a organization or
> company?
It means a release made by someone, not a random version from a git tree
somewhere. Basically something where people know where to send bug reports to.
This indeed usually means it's done by an organisation.
> Do you think it will be accepted after patch of ilp32 of kernel and glibc
> upstream?
It doesn't necessarily mean that upstream has to have accepted it already. We
just prefer to have a release tarball.
Regards,
Arnout
> I am trying to improve the glibc support for ilp32 base on the exist one
>> When it's done, can you respin your series on top of
>> master since the toolchain-external code has been updated recently ?
> Yes, of course.
>
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-02 11:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 1:16 [Buildroot] [PATCH V3 RESEND 0/5] Add ILP32 support in aarch64 Bamvor Jian Zhang
2015-08-13 1:16 ` [Buildroot] [PATCH V3 RESEND 1/5] aarch64: align aarch64_be config with aarch64s' Bamvor Jian Zhang
2015-08-13 1:16 ` [Buildroot] [PATCH V3 RESEND 2/5] aarch64: ilp32: handle special file name Bamvor Jian Zhang
2015-08-13 1:16 ` [Buildroot] [PATCH V3 RESEND 3/5] aarch64: ilp32: add ilp32 compiler and linker flags Bamvor Jian Zhang
2015-08-13 1:16 ` [Buildroot] [PATCH V3 RESEND 4/5] aarch64: ilp32: add ilp32 build config Bamvor Jian Zhang
2015-08-13 1:16 ` [Buildroot] [PATCH V3 RESEND 5/5] aarch64: ilp32 defconfig examples Bamvor Jian Zhang
2016-01-16 15:25 ` [Buildroot] [PATCH V3 RESEND 0/5] Add ILP32 support in aarch64 Romain Naour
2016-01-19 4:00 ` Bamvor Zhang Jian
2016-01-20 21:26 ` Romain Naour
2016-01-21 9:03 ` Bamvor Zhang Jian
2016-01-24 11:35 ` Romain Naour
2016-02-02 2:29 ` Zhangjian
2016-02-02 9:04 ` Romain Naour
2016-02-02 10:49 ` Zhangjian
2016-02-02 11:16 ` Arnout Vandecappelle [this message]
2016-02-03 21:11 ` Romain Naour
2016-03-20 13:10 ` Zhangjian
2016-03-20 20:33 ` Romain Naour
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=56B09008.8030202@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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