From: Luis Machado <luis.machado@arm.com>
To: Eli Zaretskii <eliz@gnu.org>, Simon Marchi <simark@simark.ca>
Cc: eggert@cs.ucla.edu, binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Disable year 2038 support on 32-bit hosts by default
Date: Mon, 8 Aug 2022 12:34:02 +0100 [thread overview]
Message-ID: <f2265af2-c588-1538-084b-7bf26f51e72c@arm.com> (raw)
In-Reply-To: <83e592ff-fa28-ddfb-a46d-79db726d2b5e@arm.com>
On 8/2/22 07:42, Luis Machado via Gdb-patches wrote:
> On 8/1/22 16:59, Eli Zaretskii wrote:
>>> Date: Mon, 1 Aug 2022 11:37:27 -0400
>>> From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
>>>
>>> My opinion would be to follow the trend and use 64-bit everywhere, and
>>> not have to worry about future-proofing anymore.
>>
>> That's not possible everywhere, though.
>>
>> And I very much doubt that time has come for us to worry about the
>> year 2038. Does anyone believe GDB 13 will still be used in that
>> year?
>
> I doubt it. There was some discussion here:
>
> https://www.mail-archive.com/bug-gnulib@gnu.org/msg41057.html
>
> I'm cc-ing Paul Eggert for additional considerations about this, but at the moment it seems the safest
> is to just use 32-bit time_t for 32-bit hosts. There were some concerns about breaking compatibility if
> we moved to 64-bit time_t on 32-bit hosts.
>
> Maybe the best course of action is to get autoconf patched to support year2038 checks and then use that
> in binutils-gdb.
Any additional thoughts on this one?
next prev parent reply other threads:[~2022-08-08 11:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 7:51 Luis Machado
2022-08-01 14:08 ` Simon Marchi
2022-08-01 14:17 ` Luis Machado
2022-08-01 15:37 ` Simon Marchi
2022-08-01 15:58 ` Eli Zaretskii
2022-08-02 6:42 ` Luis Machado
2022-08-08 11:34 ` Luis Machado [this message]
2022-08-08 11:58 ` Eli Zaretskii
2022-08-08 12:04 ` Luis Machado
2022-08-08 12:38 ` Eli Zaretskii
2022-08-08 17:55 ` Paul Eggert
2022-08-08 18:00 ` Luis Machado
2022-08-08 18:01 ` Luis Machado
2022-08-09 15:49 ` Paul Eggert
2022-08-09 15:59 ` Luis Machado
2022-08-09 16:13 ` Paul Eggert
2022-08-10 9:41 ` Nick Clifton
2022-08-10 10:14 ` Luis Machado
2022-08-09 16:29 ` Eli Zaretskii
2022-08-09 17:02 ` Paul Eggert
2022-08-10 8:38 ` Alan Modra
2022-08-08 14:51 ` Nick Clifton
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=f2265af2-c588-1538-084b-7bf26f51e72c@arm.com \
--to=luis.machado@arm.com \
--cc=binutils@sourceware.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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).