From: Andrew Pinski <pinskia@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH/AARCH64] Handle ILP32 multi-arch
Date: Fri, 07 Oct 2016 21:08:00 -0000 [thread overview]
Message-ID: <CA+=Sn1kwDEfEA3sqOnm5nZZfxsg4JuqRrYhJzFywJRbsrD9GGA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
Hi,
This patch adds ilp32 multi-arch support. This is needed to support
multi-arch on Debian like systems.
OK? Bootstrapped and tested on aarch64-linux-gnu with no regressions.
Also tested with ilp32 with a newly built toolchain that supports
ILP32 with Ubuntu 1604 base.
Thanks,
Andrew
ChangeLog:
* config/aarch64/t-aarch64-linux (MULTILIB_OSDIRNAMES): Handle
multi-arch for ilp32.
[-- Attachment #2: handleilp32_multiarch.diff.txt --]
[-- Type: text/plain, Size: 595 bytes --]
Index: gcc/config/aarch64/t-aarch64-linux
===================================================================
--- gcc/config/aarch64/t-aarch64-linux (revision 240867)
+++ gcc/config/aarch64/t-aarch64-linux (working copy)
@@ -25,4 +25,4 @@ AARCH_BE = $(if $(findstring TARGET_BIG_
MULTILIB_OSDIRNAMES = mabi.lp64=../lib64$(call if_multiarch,:aarch64$(AARCH_BE)-linux-gnu)
MULTIARCH_DIRNAME = $(call if_multiarch,aarch64$(AARCH_BE)-linux-gnu)
-MULTILIB_OSDIRNAMES += mabi.ilp32=../libilp32
+MULTILIB_OSDIRNAMES += mabi.ilp32=../libilp32$(call if_multiarch,:aarch64$(AARCH_BE)_ilp32-linux-gnu)
next reply other threads:[~2016-10-07 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 21:08 Andrew Pinski [this message]
2016-10-21 8:24 ` Andrew Pinski
2016-10-25 17:35 ` Andrew Pinski
2016-10-25 22:25 ` Matthias Klose
2016-11-11 2:58 ` Andrew Pinski
2016-12-10 21:24 ` Andrew Pinski
2017-01-03 21:04 ` Andrew Pinski
2017-02-07 23:21 ` Andrew Pinski
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='CA+=Sn1kwDEfEA3sqOnm5nZZfxsg4JuqRrYhJzFywJRbsrD9GGA@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).