From: Eero Tamminen <oak@helsinkinet.fi>
To: Finn Thain <fthain@linux-m68k.org>
Cc: libc-help@sourceware.org,
debian-68k <debian-68k@lists.debian.org>,
linux-m68k <linux-m68k@vger.kernel.org>
Subject: Re: Tuple and changes for m68k with -malign-int
Date: Tue, 29 Aug 2023 11:52:14 +0300 [thread overview]
Message-ID: <e32da2e7-3445-3fce-eb8f-242bdec0df1b@helsinkinet.fi> (raw)
In-Reply-To: <0891ec11-bed1-9120-79d5-4436dc9aee32@linux-m68k.org>
Hi,
On 29.8.2023 4.14, Finn Thain wrote:
> On Mon, 28 Aug 2023, John Paul Adrian Glaubitz wrote:
>> And since we have to break the ABI anyway to be able to use 64-bit
>> time_t
>
> If you're worried about Y2038, aren't you jumping the gun? I reckon we
> have about 10 years in which to figure out what a better m68k ABI should
> look like.
Debian is discussing LFS + time_t transition for the next release, for
all architectures. They are related, and if one needs to break /
transition ABI, doing it once is better than doing it twice...
LWN has summary of the discussion: https://lwn.net/Articles/938149/
- Eero
next prev parent reply other threads:[~2023-08-29 8:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 8:53 James Le Cuirot
2023-08-26 10:51 ` John Paul Adrian Glaubitz
2023-08-26 19:24 ` Richard
2023-08-26 20:43 ` James Le Cuirot
2023-08-28 6:54 ` Geert Uytterhoeven
2023-08-28 10:57 ` John Paul Adrian Glaubitz
2023-08-28 12:11 ` Richard
2023-08-28 12:22 ` Geert Uytterhoeven
2023-08-28 12:46 ` John Paul Adrian Glaubitz
2023-08-27 0:46 ` Finn Thain
2023-08-27 9:20 ` James Le Cuirot
2023-08-27 11:27 ` Richard
2023-08-28 7:00 ` Geert Uytterhoeven
2023-08-28 11:26 ` Richard
2023-08-28 11:40 ` Geert Uytterhoeven
2023-08-28 20:16 ` Richard
2023-08-29 6:52 ` Geert Uytterhoeven
2023-08-28 6:56 ` Geert Uytterhoeven
2023-08-28 11:13 ` John Paul Adrian Glaubitz
2023-08-29 1:12 ` Finn Thain
2023-08-28 11:10 ` John Paul Adrian Glaubitz
2023-08-28 12:44 ` Adhemerval Zanella Netto
2023-08-28 12:50 ` John Paul Adrian Glaubitz
2023-08-28 13:17 ` Andreas Schwab
2023-08-29 10:51 ` John Paul Adrian Glaubitz
2023-08-29 15:27 ` Geert Uytterhoeven
2023-08-28 13:29 ` James Le Cuirot
2023-08-29 10:54 ` John Paul Adrian Glaubitz
2023-08-29 21:53 ` Karoly Balogh
2023-08-30 1:33 ` Jeffrey Walton
2023-08-29 1:14 ` Finn Thain
2023-08-29 8:52 ` Eero Tamminen [this message]
2023-08-28 5:15 ` Florian Weimer
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=e32da2e7-3445-3fce-eb8f-242bdec0df1b@helsinkinet.fi \
--to=oak@helsinkinet.fi \
--cc=debian-68k@lists.debian.org \
--cc=fthain@linux-m68k.org \
--cc=libc-help@sourceware.org \
--cc=linux-m68k@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).