[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <917c9b03-cfd0-4bcf-d6a6-6aef7489b27b@physik.fu-berlin.de>
Date: Thu, 14 May 2020 10:24:25 +0200
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: Christian Brauner <christian.brauner@...ntu.com>
Cc: "Luck, Tony" <tony.luck@...el.com>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Arnd Bergmann <arnd@...db.de>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Qais Yousef <qais.yousef@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ia64: enable HAVE_COPY_THREAD_TLS, switch to
kernel_clone_args
Hi!
On 5/14/20 9:58 AM, Christian Brauner wrote:
>> The machine also serves as a Debian buildd which is why it's a bit more
>> busy than other servers.
>
> Oh? Does it also produce Debian images for ia64 similar to what is done
> for sparc64?
Yes, it's actually the same person who does this - me ;).
These images should work just fine:
> https://cdimage.debian.org/cdimage/ports/2020-04-19/
The latest snapshot is currently broken due to a regression in initramfs-tools.
>>>> As for getting a working cross-compiler for ia64 in Debian, this has
>>>> been on my TODO list for a while now. Building a cross-compiler for
>>>> ia64 is a bit more tricky due to it's dependency on the external
>>>> libunwind.
>>>
>>> I hit that roadblock as well but yeah, a cross-compiler would be
>>> helpful.
>>
>> It's not difficult, it's just a bit of annoying package work including
>> some trial and error testing.
>>
>> Once the cross-compiler is in Debian, it will be available in Ubuntu as well.
>
> Would that based on a recent gcc? I vaguely remember a post somwhere
> that gcc 10 or 11 was planning to drop support for ia64?
Yes, that would be the latest gcc. There are no plans at the moment to
drop ia64 from gcc as the backend is already ported to MODE_CC.
m68k was on the brink of being removed, but I started a Bountysource campaign
to convert it from cc0 to MODE_CC and it was eventually saved ;).
> https://www.bountysource.com/issues/80706251-m68k-convert-the-backend-to-mode_cc-so-it-can-be-kept-in-future-releases
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@...ian.org
`. `' Freie Universitaet Berlin - glaubitz@...sik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Powered by blists - more mailing lists