From: "Arsen Arsenović" <arsen@aarsen.me>
To: Florian Weimer <fweimer@redhat.com>
Cc: Adam Sampson <ats@offog.org>,
Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>,
Sam James <sam@gentoo.org>,
autoconf@gnu.org, c-std-porting@lists.linux.dev,
Zack Weinberg <zack@owlfolio.org>,
David Seifert <soap@gentoo.org>,
Gentoo Toolchain <toolchain@gentoo.org>,
Paul Eggert <eggert@cs.ucla.edu>,
Frederic Berat <fberat@redhat.com>
Subject: Re: On time64 and Large File Support
Date: Tue, 15 Nov 2022 08:39:45 +0100 [thread overview]
Message-ID: <868rkcvdmi.fsf@aarsen.me> (raw)
In-Reply-To: <87sfiltg14.fsf@oldenburg.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
Morning,
Florian Weimer <fweimer@redhat.com> writes:
> Uhm, this seems to be something affecting 64-bit targets, not 32-bit
> targets, after the POSIX fix went in? We have a few more such quirks.
> (I understood the question to be about cleanup opportunities for 32-bit
> architectures.)
Hmm, yes, not sure what he meant. The ABI being fine on 32-bit slipped
by me when forwarding. I'll forward any clarification.
Have a great day.
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
next prev parent reply other threads:[~2022-11-15 8:14 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 8:38 On time64 and Large File Support Sam James
2022-11-11 9:16 ` Paul Eggert
2022-11-11 9:19 ` Sam James
2022-11-11 23:48 ` Joseph Myers
2022-11-11 9:19 ` Florian Weimer
2022-11-11 9:27 ` Sam James
2022-11-11 11:38 ` Florian Weimer
2022-11-11 20:12 ` Paul Eggert
2022-11-12 2:20 ` Zack Weinberg
2022-11-12 3:57 ` Sam James
2022-11-12 14:16 ` Zack Weinberg
2022-11-12 17:41 ` Paul Eggert
2022-11-12 18:50 ` Bruno Haible
2022-11-12 19:15 ` Paul Eggert
2022-11-12 20:23 ` Wookey
2022-11-12 20:54 ` Russ Allbery
2022-11-12 21:31 ` Paul Eggert
[not found] ` <951fc967-042c-4978-bd78-8bc4c8706b18@app.fastmail.com>
2022-11-13 5:11 ` Zack Weinberg
2022-11-15 5:06 ` Sam James
2022-12-25 19:19 ` Paul Eggert
2022-12-29 4:02 ` Zack Weinberg
2022-12-30 22:12 ` Paul Eggert
2022-12-30 22:20 ` Sam James
2023-01-20 9:56 ` Paul Eggert
2023-02-02 6:43 ` Sam James
2023-02-02 23:15 ` time for Autoconf 2.72 (was: On time64 and Large File Support) Paul Eggert
2023-02-02 23:17 ` Zack Weinberg
2023-02-03 5:49 ` Sam James
2023-02-03 12:43 ` time for Autoconf 2.72 Bruno Haible
[not found] ` <CAObJKZp2CCRR46-X9NYaRES7eDCVyoJ0xv=u4aSG2KeQv4vtjA@mail.gmail.com>
2023-02-27 2:30 ` time for Autoconf 2.72 (was: On time64 and Large File Support) Sam James
2023-03-17 23:47 ` Sam James
2023-03-18 0:59 ` Paul Eggert
2023-03-18 2:08 ` Jim Meyering
2023-03-18 2:52 ` Paul Eggert
2023-03-19 0:30 ` Jim Meyering
2023-03-19 0:57 ` Sam James
2022-11-15 5:09 ` On time64 and Large File Support Sam James
2022-11-12 18:19 ` Paul Eggert
2022-11-11 9:40 ` Andreas K. Huettel
2022-11-11 11:30 ` Florian Weimer
2022-11-11 19:01 ` Andreas K. Huettel
2022-11-11 19:28 ` Palmer Dabbelt
2022-11-11 9:46 ` Paul Eggert
2022-11-11 11:22 ` Florian Weimer
2022-11-11 19:56 ` Paul Eggert
2022-11-12 4:20 ` Wookey
2022-11-12 4:28 ` Sam James
2022-11-12 4:56 ` Wookey
2022-11-12 4:59 ` Sam James
2022-11-12 18:33 ` Paul Eggert
2022-11-14 8:39 ` Adam Sampson
2022-11-14 11:47 ` Florian Weimer
2022-11-14 20:26 ` Arsen Arsenović
2022-11-14 20:52 ` Florian Weimer
2022-11-15 7:39 ` Arsen Arsenović [this message]
2022-11-11 10:25 ` Richard Purdie
2023-03-01 22:38 ` Eric Blake
2023-03-02 0:29 ` Demi Marie Obenour
2023-03-02 9:04 ` Daniel P. Berrangé
2023-03-02 10:28 ` Paul Eggert
2023-03-02 10:38 ` Andreas Schwab
2023-03-03 5:46 ` Paul Eggert
2023-03-06 8:58 ` Andreas Schwab
2023-03-06 10:19 ` Florian Weimer
2023-03-02 11:02 ` Richard W.M. Jones
2023-03-02 12:17 ` Bruno Haible
2023-03-02 13:24 ` Daniel P. Berrangé
2023-03-03 3:30 ` Wookey
2023-03-03 5:50 ` Paul Eggert
2023-03-03 14:01 ` Wookey
2023-03-03 14:14 ` Daniel P. Berrangé
2023-03-03 23:21 ` Arsen Arsenović
2023-03-03 11:49 ` Florian Weimer
2023-03-03 12:39 ` Richard W.M. Jones
2023-03-02 8:30 ` Richard W.M. Jones
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=868rkcvdmi.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=ats@offog.org \
--cc=autoconf@gnu.org \
--cc=c-std-porting@lists.linux.dev \
--cc=eggert@cs.ucla.edu \
--cc=fberat@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=sam@gentoo.org \
--cc=soap@gentoo.org \
--cc=toolchain@gentoo.org \
--cc=zack@owlfolio.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