From: Christian Brauner <christian.brauner@ubuntu.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>, Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Qais Yousef <qais.yousef@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ia64: enable HAVE_COPY_THREAD_TLS, switch to kernel_clone_args
Date: Thu, 14 May 2020 08:37:39 +0000 [thread overview]
Message-ID: <20200514083739.m2idxcxof4jyreck@wittgenstein> (raw)
In-Reply-To: <917c9b03-cfd0-4bcf-d6a6-6aef7489b27b@physik.fu-berlin.de>
On Thu, May 14, 2020 at 10:24:25AM +0200, John Paul Adrian Glaubitz wrote:
> 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 ;).
Well thank you very much. Thanks to this I was able to test my sparc
patches in qemu. :)
>
> These images should work just fine:
>
> > https://cdimage.debian.org/cdimage/ports/2020-04-19/
Oh I didn't find these images when searching for them. They would be
super helpful but there's no qemu for ia64 anymore that's useable. I had
tried building qemu from an old source based on a gsoc project for an
ia64 port but that turned out to be more involved than writing ia64
assembly itself. :)
>
> 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
Oh that's pretty neat. Thanks!
Christian
next prev parent reply other threads:[~2020-05-14 8:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 20:48 [PATCH] ia64: enable HAVE_COPY_THREAD_TLS, switch to kernel_clone_args Christian Brauner
2020-05-13 21:19 ` Luck, Tony
2020-05-13 21:26 ` John Paul Adrian Glaubitz
2020-05-14 7:46 ` Christian Brauner
2020-05-14 7:53 ` John Paul Adrian Glaubitz
2020-05-14 7:58 ` Christian Brauner
2020-05-14 8:24 ` John Paul Adrian Glaubitz
2020-05-14 8:37 ` Christian Brauner [this message]
2020-05-14 8:51 ` John Paul Adrian Glaubitz
2020-05-14 9:48 ` John Paul Adrian Glaubitz
2020-05-14 10:04 ` Christian Brauner
2020-05-14 10:08 ` John Paul Adrian Glaubitz
2020-05-14 10:15 ` Christian Brauner
2020-05-14 10:19 ` Christian Brauner
2020-05-14 10:21 ` John Paul Adrian Glaubitz
2020-05-14 10:32 ` Christian Brauner
2020-05-14 10:35 ` John Paul Adrian Glaubitz
2020-05-14 10:39 ` Christian Brauner
2020-05-14 10:37 ` Christian Brauner
2020-05-14 10:45 ` Andreas Schwab
2020-05-14 10:51 ` Christian Brauner
2020-05-14 10:37 ` Andreas Schwab
2020-05-14 13:00 ` Christian Brauner
2020-05-14 8:58 ` Sebastian Andrzej Siewior
2020-05-14 9:57 ` Christian Brauner
2020-05-14 7:50 ` Christian Brauner
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=20200514083739.m2idxcxof4jyreck@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=fenghua.yu@intel.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=qais.yousef@arm.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=viro@zeniv.linux.org.uk \
/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