public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Bamvor Jian Zhang <bamvor.zhangjian@huawei.com>
To: ltp-list@lists.sourceforge.net
Cc: Bintian <bintian.wang@huawei.com>, apinski@cavium.com
Subject: Re: [LTP] [RFC PATCH 0/3] bugfix for aarch64 ILP32
Date: Thu, 19 Mar 2015 13:23:23 +0800	[thread overview]
Message-ID: <550A5D4B.5090009@huawei.com> (raw)
In-Reply-To: <1426675580-28835-1-git-send-email-bamvor.zhangjian@huawei.com>

On 2015/3/18 18:46, Zhang Jian(Bamvor) wrote:
> Hi,
Hi, guys

These series patches should go libc-alpha[1], sorry for confuse.
Here is the right series my want to post[2].

regards

bamvor

[1] https://sourceware.org/ml/libc-alpha/2015-03/msg00586.html
[2] http://sourceforge.net/p/ltp/mailman/ltp-list/thread/1426742198-17967-1-git-send-email-bamvor.zhangjian%40huawei.com/#msg33613777

> This is bamvor from Huawei OS team. We test ILP32 support through
> LTP testcases for both little endian and big endian. There are some
> failures we thought they should be fixed in glibc level, so, here they are.
> 
> Hope these series of patch could help other people who is interested
> in ILP32 in aarch64. We will send another series in LTP mailing list about
> LTP relative patches.
> 
> These work is base on Andrew's ilp32 patch [ilp32 v3 patch]
> [ilp32_glibc_patch].
> 
> The test of build is based on the toolchain built by linaro ABE environment
> [linaro_abe].
> 
> [ilp32 v3 patch] (https://lkml.org/lkml/2014/9/3/704)
> [ilp32_glibc_patch] (https://sourceware.org/ml/libc-alpha/2014-10/msg00596.html)
> [linaro_abe] (https://wiki.linaro.org/ABE)
> 
> Yang Yingliang (3):
>   ARM64: ILP32: change register x1 to PTR_REG
>   ARM64: ILP32: use __fsword_t in generic/bits/statfs.h
>   ARM64: ILP32: change register x##R to PTR_REG (R)
> 
>  sysdeps/aarch64/sysdep.h                      |  2 +-
>  sysdeps/unix/sysv/linux/aarch64/sysdep.h      |  2 +-
>  sysdeps/unix/sysv/linux/generic/bits/statfs.h | 24 ++++++++++++------------
>  3 files changed, 14 insertions(+), 14 deletions(-)
> 



------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

           reply	other threads:[~2015-03-19  5:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1426675580-28835-1-git-send-email-bamvor.zhangjian@huawei.com>]

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=550A5D4B.5090009@huawei.com \
    --to=bamvor.zhangjian@huawei.com \
    --cc=apinski@cavium.com \
    --cc=bintian.wang@huawei.com \
    --cc=ltp-list@lists.sourceforge.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