From: Andrew Pinski <pinskia@gmail.com>
To: Matthias Klose <doko@debian.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>,
Richard Earnshaw <richard.earnshaw@arm.com>,
James Greenhalgh <james.greenhalgh@arm.com>
Subject: Re: [PATCH/AARCH64] Handle ILP32 multi-arch
Date: Tue, 07 Feb 2017 23:21:00 -0000 [thread overview]
Message-ID: <CA+=Sn1=YVre+GPET9pDdN2A7q5SgkZVZf8QjoqVZK-e6eP75CA@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1kSbf_nf2vkvg3t=e6MyPWGWKpCawuPaCKOiBW4YC=bDQ@mail.gmail.com>
On Tue, Jan 3, 2017 at 1:04 PM, Andrew Pinski <pinskia@gmail.com> wrote:
> Ping?
>
> On Sat, Dec 10, 2016 at 1:24 PM, Andrew Pinski <pinskia@gmail.com> wrote:
>> On Thu, Nov 10, 2016 at 6:58 PM, Andrew Pinski <pinskia@gmail.com> wrote:
>>> On Tue, Oct 25, 2016 at 3:25 PM, Matthias Klose <doko@debian.org> wrote:
>>>> On 07.10.2016 23:08, Andrew Pinski wrote:
>>>>> 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.
>>>>
>>>> I can't approve that, but it looks like a reasonable change, but we should
>>>> document the multiarch triplet at https://wiki.debian.org/Multiarch/Tuples
>>>
>>>
>>> Ping?
>>
>> Ping? This is the only outstanding GCC ILP32 related patch.
Ping x4?
>>
>>>
>>> Thanks,
>>> Andrew
>>>
>>>>
>>>> Matthias
>>>>
prev parent reply other threads:[~2017-02-07 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 21:08 Andrew Pinski
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 [this message]
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+=Sn1=YVre+GPET9pDdN2A7q5SgkZVZf8QjoqVZK-e6eP75CA@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=doko@debian.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=james.greenhalgh@arm.com \
--cc=marcus.shawcroft@arm.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=richard.earnshaw@arm.com \
/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).