From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Luis Machado <luis.machado@arm.com>
Cc: simark@simark.ca, 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, 08 Aug 2022 15:38:42 +0300 [thread overview]
Message-ID: <83wnbivrjh.fsf@gnu.org> (raw)
In-Reply-To: <b56f55fe-ad62-904c-b2c6-4ffd9afccc46@arm.com> (message from Luis Machado on Mon, 8 Aug 2022 13:04:58 +0100)
> Date: Mon, 8 Aug 2022 13:04:58 +0100
> Cc: simark@simark.ca, eggert@cs.ucla.edu, binutils@sourceware.org,
> gdb-patches@sourceware.org
> From: Luis Machado <luis.machado@arm.com>
>
> >> Any additional thoughts on this one?
> >
> > What is the current plan if no one else chimes in?
>
> I'd like to push this temporary fix in so we can at least have a functional 32-bit Arm GDB on 32-bit hosts supporting
> 64-bit time_t. I expect other 32-bit GDB's will also potentially run into this.
I don't object to that.
Thanks.
next prev parent reply other threads:[~2022-08-08 12:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 7:51 Luis Machado via Gdb-patches
2022-08-01 14:08 ` Simon Marchi via Gdb-patches
2022-08-01 14:17 ` Luis Machado via Gdb-patches
2022-08-01 15:37 ` Simon Marchi via Gdb-patches
2022-08-01 15:58 ` Eli Zaretskii via Gdb-patches
2022-08-02 6:42 ` Luis Machado via Gdb-patches
2022-08-08 11:34 ` Luis Machado via Gdb-patches
2022-08-08 11:58 ` Eli Zaretskii via Gdb-patches
2022-08-08 12:04 ` Luis Machado via Gdb-patches
2022-08-08 12:38 ` Eli Zaretskii via Gdb-patches [this message]
2022-08-08 17:55 ` Paul Eggert
2022-08-08 18:00 ` Luis Machado via Gdb-patches
2022-08-08 18:01 ` Luis Machado via Gdb-patches
2022-08-09 15:49 ` Paul Eggert
2022-08-09 15:59 ` Luis Machado via Gdb-patches
2022-08-09 16:13 ` Paul Eggert
2022-08-10 9:41 ` Nick Clifton via Gdb-patches
2022-08-10 10:14 ` Luis Machado via Gdb-patches
2022-08-09 16:29 ` Eli Zaretskii via Gdb-patches
2022-08-09 17:02 ` Paul Eggert
2022-08-10 8:38 ` Alan Modra via Gdb-patches
2022-08-08 14:51 ` Nick Clifton via Gdb-patches
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=83wnbivrjh.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=binutils@sourceware.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=luis.machado@arm.com \
--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