Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/5] Add ILP32 support in aarch64
Date: Tue, 17 Mar 2015 14:49:25 -0300	[thread overview]
Message-ID: <55086925.3080102@zacarias.com.ar> (raw)
In-Reply-To: <CAOijeYJLdrDiOnYJ2fvPWi2peT56rTALryg7jgB-gJ_X0J5UBA@mail.gmail.com>

On 03/17/2015 11:44 AM, Bamvor Zhang wrote:

>> 1) You're using -mabi unconditionally.
>> Current default gcc is 4.8.x which doesn't understand -mabi for aarch64.
> Yes.

This is bad for the scenario where gcc = default = 4.8.x and we use lp64
(default as well).
Since you're setting BR2_GCC_TARGET_ABI to lp64 in patch 4 and this is
used in package/gcc/gcc.mk it causes breakage for: internal toolchain,
aarch64 BE or LE, lp64.
Just make it empty, it's the default for gcc and that won't change:

arch/Config.in.aarch64 -> default "" if BR2_AARCH64_LP64

It's not "pretty" but it works just fine and reflects previous behaviour.

>> This will only fix the ILP32 problem, doesn't help for -mabi=lp64 though
>> (point 1).
> Well, do you mean I should handle -mabi=lp64 as well? It is the default
> api in aarch64 gcc 4.9.x. It may be useful when build the kernel.

See solution above.

>> 3) ILP32 little endian doesn't build with gcc 4.9.x/binutils 2.25/glibc
>> 2.20: it results in an internal compiler error while building glibc, so
>> very likely gcc's fault. This should be handled as well, by fixing it or
>> disabling the internal toolchain backend for this combination.
> I guess linaro has the patch in it while I hope I could deal with it
> after the external toolchain patches is accept. Do you comfortable with
> only external toolchain support at this time?

Yes that's not a problem, it'll probably be part of some future release
and then we can unleash it.
Or add the patch(es) if they're small and non-intrusive.
Regardless it may be an external-only option at this point since ILP32
is labelled as beta all over the place.
Regards.

  reply	other threads:[~2015-03-17 17:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 10:00 [Buildroot] [PATCH 0/5] Add ILP32 support in aarch64 Zhang Jian
2015-03-16 10:00 ` [Buildroot] [PATCH 1/5] aarch64: add big endian(aarch64_be) support Zhang Jian
2015-03-16 10:00 ` [Buildroot] [PATCH 2/5] aarch64: ilp32: handle special file name Zhang Jian
2015-03-17 10:27   ` Steven Noonan
2015-03-17 14:31     ` Bamvor Zhang
2015-03-16 10:00 ` [Buildroot] [PATCH 3/5] aarch64: ilp32: add ilp32 compiler and linker flags Zhang Jian
2015-03-16 10:00 ` [Buildroot] [PATCH 4/5] aarch64: ilp32: add ilp32 menuconfig Zhang Jian
2015-03-16 10:00 ` [Buildroot] [PATCH 5/5] aarch64: ilp32 defconfig examples Zhang Jian
2015-03-17 13:30 ` [Buildroot] [PATCH 0/5] Add ILP32 support in aarch64 Gustavo Zacarias
2015-03-17 14:44   ` Bamvor Zhang
2015-03-17 17:49     ` Gustavo Zacarias [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-20 11:25 Zhang Jian

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=55086925.3080102@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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