From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
"H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@kernel.org>
Subject: Re: [PATCH] x86: Start removing X86_X32_ABI
Date: Mon, 1 Jun 2026 23:12:09 +0200 [thread overview]
Message-ID: <20260601211209.WIms_QkR@linutronix.de> (raw)
In-Reply-To: <afa7ec338c931cc6fba15e2d37fcbbfc7670e3d5.camel@physik.fu-berlin.de>
On 2026-05-27 17:57:30 [+0200], John Paul Adrian Glaubitz wrote:
> Hello Sebastian,
Hi Adrian,
> Debian still has an x32 port which is building unstable packages, see [1].
I am aware that Debian has this.
> Even Rust works there.
Even rust. You have approx. ~72% of packages
https://buildd.debian.org/stats/graph-ports-week-big.png
and peaked at ~90% in 2016 and then again shortly before 2022
https://buildd.debian.org/stats/graph-ports-big.png
Some of the big ones are missing like libreoffice, firefox or chromium.
In 2012 x32 was introduced. Around 2013 if I am not mistaken x32 entered
d-ports. This is where we still are. That is why I think it is time to
let it rest.
Debian Squeeze and Wheezy had kfreebsd as a tech-preview, sadly not
more.
>
> Adrian
Sebastian
next prev parent reply other threads:[~2026-06-01 21:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 9:37 [PATCH] x86: Start removing X86_X32_ABI Sebastian Andrzej Siewior
2026-05-23 21:43 ` H. Peter Anvin
2026-05-26 10:40 ` Sebastian Andrzej Siewior
2026-05-26 15:53 ` H. Peter Anvin
2026-05-26 15:54 ` H. Peter Anvin
2026-05-26 20:43 ` Sebastian Andrzej Siewior
2026-05-31 21:46 ` Arnd Bergmann
2026-06-01 21:44 ` Sebastian Andrzej Siewior
2026-06-01 22:45 ` Arnd Bergmann
2026-05-27 12:02 ` David Laight
2026-06-01 21:29 ` H. Peter Anvin
2026-06-04 20:27 ` Thomas Gleixner
2026-05-27 13:10 ` Sam James
2026-05-27 13:41 ` Neal Gompa
2026-05-27 15:57 ` John Paul Adrian Glaubitz
2026-06-01 21:12 ` Sebastian Andrzej Siewior [this message]
2026-06-01 21:14 ` H. Peter Anvin
2026-05-28 7:05 ` Tomas Glozar
2026-06-01 21:26 ` Sebastian Andrzej Siewior
2026-05-31 22:05 ` Arnd Bergmann
2026-06-02 16:02 ` Maciej W. Rozycki
2026-06-02 16:36 ` Arnd Bergmann
2026-06-05 3:35 ` H. Peter Anvin
2026-06-02 9:48 ` Richard Purdie
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=20260601211209.WIms_QkR@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.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