Add ILP32 support in aarch64
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest posting 6/60 of 5 patches 0 repliesNew
- v3 posting 5/60 of 5 patches 0 repliesSuperseded
- v3 posting 4/60 of 5 patches 0 repliesSuperseded
Earlier versions · 3
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v3 posting 3/6 | 0 of 5 patches | 0 replies | Superseded | |
| v3 posting 2/6 | 0 of 5 patches | 0 replies | Superseded | |
| v3 posting 1/6 | 0 of 5 patches | 0 replies | Superseded |
Patches in v3 posting 6/6 No applies recorded yet
None of the 5 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [Buildroot] [PATCH V3 RESEND 0/5] Add ILP32 support in aarch64
Hi Bamvor, All,
Le 20/03/2016 14:10, Zhangjian (Bamvor) a ?crit :
Quoted 2 lines
Hi, Romain, Arnout, all
[snip]
Quoted 11 lines
Quoted 11 lines
Quoted 6 lines
Quoted 3 lines
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.See as example the toolchains provided by Imagination Technologies [1] or Synopsys [2]. All their patches they are using may not upstream yet, but they provide a working toolchain which is pretty well tested.
Quoted 7 lines
Quoted 2 lines
[1] http://codescape-mips-sdk.imgtec.com/components/toolchain/2015.06-05/
[2] https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/In recent linaro connect, there is a presentation[1] about the performance of ilp32.
And in its homepage[2], there is a script[3] for building the ilp32 compiler. At this pointer, are you intertested in review the patches of ilp32 if I send a new series?
Thanks for the news about ilp32 support in aarch64.
Since your previous patches doesn't apply anymore on the master branch we have marked them "Changes requested" in the patchwork. However, I added a new entry in our TODO list [1] in order to not forget them.
The first problem is: how to build a working ipl32 toolchain ?
* With the abe script I wasn't able to build one due to some build issue with glibc. Also the abe script was from an experimental/unstable branch.
* With build_ilp32_toolchain.sh script we need to build the toolchain as root
[2] which is not recommended. Also the kernel header is directly imported from the host machine (from /usr/include). I guess an ilp32 toolchain needs some specific or modified kernel header in order to support ilp32 based system.
* There is no aarch64 ilp32 prebuild toolchain available.
It seems that the number of patches is quite limited [4], so maybe you can use the Buildroot internal toolchain infra to build the toolchain, and use a specific source version for gcc, binutils and glibc and include all needed patches.
Do you know if each ilp32 patches can be easily applied on binutils and glibc official release ? Otherwise you can simply use the hashes provided by leapproject wiki [4].
For gcc it's a bit complicated since the patches are for the Linaro GCC 4.9.3, not sure it will apply/work with a vanilla gcc 4.9.3. Also gcc-prequisites-aarch64_ilp32-target-autoconf.patch is quite huge and need to be split into several patches...
But this require a lot of work.
So, in the end, it would be easier if you provide a prebuild ilp32 toolchain tarball (like Arnout suggest) with your new series.
To answer your question.
Yes, I'm interested in reviewing your ilp32 series but I need a toolchain to test it :)
Best regards,
Romain
[1] http://elinux.org/Buildroot#Toolchain
[2]
https://github.com/leapproject/ilp32-toolchain/blob/master/build_ilp32_toolchain.sh#L15
[3]
https://github.com/leapproject/ilp32-toolchain/blob/master/build_ilp32_toolchain.sh#L112
[4]
https://wiki.leapproject.ca/index.php?title=AArch64_ILP32_Toolchain#Sources_and_Patches