linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Glaser <tg@debian.org>
To: Finn Thain <fthain@linux-m68k.org>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	 linux-m68k <linux-m68k@vger.kernel.org>,
	 debian-68k <debian-68k@lists.debian.org>,
	 James Le Cuirot <chewi@aura-online.co.uk>,
	Sam James <sam@gentoo.org>,
	 Geert Uytterhoeven <geert@linux-m68k.org>,
	 Andreas Schwab <schwab@linux-m68k.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: Plan needed for switching m68k to 32-bit alignment
Date: Sun, 27 Oct 2024 00:04:18 +0200 (CEST)	[thread overview]
Message-ID: <5e8917a2-b7c4-6c06-e63f-1f05eea32120@mirbsd.de> (raw)
In-Reply-To: <eb26c030-5bc9-0e2e-1222-64306bfa7553@linux-m68k.org>

On Sat, 26 Oct 2024, Finn Thain wrote:

>> The following packages require 32-bit alignment:
>>
>> - mold
>> - LLVM
>> - gccgo
>> - Qt5 (several packages affected)
>> - Qt6 (several packages affected)
>> - OpenJDK (all versions)
>> - Python >= 3.13
>> - Rust
>
>That seems to imply that someone requires that those packages are ported.

Yes, we do. Rust especially is killing the entire FOSS ecosystem.

These all are conditio sine qua nōn when it comes to continuing
Linux/m68k, as a whole.

>Absent the right conditions, perhaps it is best focus limited porter and
>developer effort on patching only those packages that are really required.

I tried my hand at Qt5. About 20 man-hours in I essentially gave up,
and that was without even getting to something I could put to a
compile and runtime test.

“Natural” alignment of data types has essentially become a requirement
these days, and m68k is the only true outlyer (i386 could in theory, but
the Unix psABI designers were sensible enough to not do it).

bye,
//mirabilos
-- 
<igli> exceptions: a truly awful implementation of quite a nice idea.
<igli> just about the worst way you could do something like that, afaic.
<igli> it's like anti-design.  <mirabilos> that too… may I quote you on that?
<igli> sure, tho i doubt anyone will listen ;)

  reply	other threads:[~2024-10-26 22:04 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25  6:48 Plan needed for switching m68k to 32-bit alignment John Paul Adrian Glaubitz
2024-10-25  9:06 ` Finn Thain
2024-10-25  9:18   ` John Paul Adrian Glaubitz
2024-10-26  7:31     ` Finn Thain
2024-10-26 22:04       ` Thorsten Glaser [this message]
2024-10-27  2:49         ` Finn Thain
2024-10-27  3:08           ` Thorsten Glaser
2024-10-27  3:47             ` Finn Thain
2024-10-27  4:23               ` Thorsten Glaser
2024-10-27  6:16                 ` Finn Thain
2024-10-27 13:15                   ` Arnd Bergmann
2024-10-28  3:07                     ` Thorsten Glaser
2024-10-28  4:51                       ` Finn Thain
2024-10-28  8:09                         ` John Paul Adrian Glaubitz
2024-10-28  8:49                           ` Finn Thain
2024-11-13 12:53                             ` John Paul Adrian Glaubitz
2024-10-28  8:03                       ` John Paul Adrian Glaubitz
2024-10-28  8:44                         ` Finn Thain
2024-11-13 12:51                           ` John Paul Adrian Glaubitz
2024-10-28  7:58                     ` John Paul Adrian Glaubitz
2024-10-28  7:55                   ` John Paul Adrian Glaubitz
2024-11-14 16:29                   ` Geert Uytterhoeven
2024-11-15  0:24                     ` Finn Thain
2024-11-15  1:24                       ` Thorsten Glaser
2024-11-15  1:31                         ` Thorsten Glaser
2024-10-28  7:53               ` John Paul Adrian Glaubitz
2024-10-28  7:49             ` John Paul Adrian Glaubitz
2024-10-28  7:47           ` John Paul Adrian Glaubitz
2024-10-28  8:40             ` Finn Thain
2024-11-13 12:50               ` John Paul Adrian Glaubitz
2024-11-13 22:01                 ` Finn Thain
2024-10-28  7:43         ` John Paul Adrian Glaubitz
2024-10-28  7:40       ` John Paul Adrian Glaubitz
2024-10-28  8:29         ` Finn Thain
2024-11-13 12:47           ` John Paul Adrian Glaubitz
2024-11-13 22:52             ` Finn Thain
2024-10-25  9:55 ` Arnd Bergmann
2024-10-25 10:10   ` John Paul Adrian Glaubitz
2024-10-25 10:50     ` Arnd Bergmann
2024-10-25 15:07       ` Andreas Schwab
2024-10-28  7:24         ` John Paul Adrian Glaubitz
2024-10-25 21:38     ` Thorsten Glaser
2024-10-25 22:24       ` Andreas Schwab
2024-10-25 23:42         ` Thorsten Glaser
2024-10-27 13:03           ` Greg Ungerer
2024-10-27 12:58         ` Arnd Bergmann
2024-10-28  3:19           ` Thorsten Glaser
2024-10-28  3:54             ` Greg Ungerer
2024-10-28  7:57           ` John Paul Adrian Glaubitz
2024-10-28  7:30         ` John Paul Adrian Glaubitz
2024-10-26 10:46       ` Geert Uytterhoeven
2024-10-28  7:41         ` John Paul Adrian Glaubitz
2024-10-28  7:26       ` John Paul Adrian Glaubitz
2024-11-14 19:46       ` Geert Uytterhoeven
2024-11-14 22:13         ` Thorsten Glaser
2024-11-14 22:37           ` James Le Cuirot
2024-10-28 18:57   ` Michael Schmitz
2024-10-29  3:39     ` Finn Thain
2024-11-13 12:58       ` John Paul Adrian Glaubitz
2024-11-13 23:12         ` Finn Thain
2024-11-13 12:54     ` John Paul Adrian Glaubitz
2024-11-13 18:36       ` Michael Schmitz
2024-11-13 19:55         ` John Paul Adrian Glaubitz
2024-11-13 20:48           ` Stan Johnson
2024-11-13 21:01             ` John Paul Adrian Glaubitz
2024-11-14 18:07               ` Stan Johnson
2024-11-14 19:28                 ` Geert Uytterhoeven
2024-11-13 20:49           ` John Paul Adrian Glaubitz
2024-11-13 21:33           ` Thorsten Glaser
2024-11-13 23:34             ` Finn Thain
2024-11-14 19:32           ` Geert Uytterhoeven

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=5e8917a2-b7c4-6c06-e63f-1f05eea32120@mirbsd.de \
    --to=tg@debian.org \
    --cc=arnd@arndb.de \
    --cc=chewi@aura-online.co.uk \
    --cc=debian-68k@lists.debian.org \
    --cc=fthain@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@vger.kernel.org \
    --cc=sam@gentoo.org \
    --cc=schwab@linux-m68k.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 NNTP newsgroup(s).