public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: schwab@suse.de (Andreas Schwab)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 resend 00/20] ILP32 for ARM64
Date: Tue, 11 Apr 2017 13:54:15 +0200	[thread overview]
Message-ID: <mvmbms3b1nc.fsf@suse.de> (raw)
In-Reply-To: <20170411113334.GA27857@e104818-lin.cambridge.arm.com> (Catalin Marinas's message of "Tue, 11 Apr 2017 12:33:35 +0100")

On Apr 11 2017, Catalin Marinas <catalin.marinas@arm.com> wrote:

> Is there an up to date pre-built toolchain and a filesystem for ILP32?

https://build.opensuse.org/project/show/devel:ARM:Factory:Contrib:ILP32
should have everything you need.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab at suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2017-04-11 11:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01 19:19 [PATCH v7 resend 00/20] ILP32 for ARM64 Yury Norov
2017-03-01 19:19 ` [PATCH 01/20] compat ABI: use non-compat openat and open_by_handle_at variants Yury Norov
2017-03-01 19:19 ` [PATCH 02/20] 32-bit ABI: introduce ARCH_32BIT_OFF_T config option Yury Norov
2017-03-01 19:19 ` [PATCH 04/20] arm64: ilp32: add documentation on the ILP32 ABI for ARM64 Yury Norov
2017-03-01 19:19 ` [PATCH 05/20] arm64: rename COMPAT to AARCH32_EL0 in Kconfig Yury Norov
2017-03-01 19:19 ` [PATCH 06/20] arm64: ensure the kernel is compiled for LP64 Yury Norov
2017-03-01 19:19 ` [PATCH 07/20] arm64:uapi: set __BITS_PER_LONG correctly for ILP32 and LP64 Yury Norov
2017-03-01 19:19 ` [PATCH 08/20] thread: move thread bits accessors to separated file Yury Norov
2017-03-01 19:19 ` [PATCH 09/20] arm64: introduce is_a32_task and is_a32_thread (for AArch32 compat) Yury Norov
2017-03-01 19:19 ` [PATCH 10/20] arm64: ilp32: add is_ilp32_compat_{task, thread} and TIF_32BIT_AARCH64 Yury Norov
2017-03-01 19:19 ` [PATCH 11/20] arm64: introduce binfmt_elf32.c Yury Norov
2017-03-01 19:19 ` [PATCH 12/20] arm64: ilp32: introduce binfmt_ilp32.c Yury Norov
2017-03-01 19:19 ` [PATCH 13/20] arm64: ilp32: share aarch32 syscall handlers Yury Norov
2017-03-01 19:19 ` [PATCH 14/20] arm64: ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it Yury Norov
2017-03-01 19:19 ` [PATCH 15/20] arm64: signal: share lp64 signal routines to ilp32 Yury Norov
2017-03-01 19:19 ` [PATCH 16/20] arm64: signal32: move ilp32 and aarch32 common code to separated file Yury Norov
2017-03-01 19:19 ` [PATCH 17/20] arm64: ilp32: introduce ilp32-specific handlers for sigframe and ucontext Yury Norov
2017-03-01 19:19 ` [PATCH 18/20] arm64: ptrace: handle ptrace_request differently for aarch32 and ilp32 Yury Norov
2017-03-01 19:19 ` [PATCH 19/20] arm64:ilp32: add vdso-ilp32 and use for signal return Yury Norov
2017-03-01 19:19 ` [PATCH 20/20] arm64:ilp32: add ARM64_ILP32 to Kconfig Yury Norov
2017-04-10 19:47 ` [PATCH v7 resend 00/20] ILP32 for ARM64 Yury Norov
2017-04-11 11:33   ` Catalin Marinas
2017-04-11 11:54     ` Andreas Schwab [this message]
2017-04-11 13:33     ` Yury Norov
2017-04-11 18:36     ` Yury Norov
2017-04-11 18:42       ` Florian Weimer
2017-04-11 20:52         ` Yury Norov

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=mvmbms3b1nc.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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