From: Joel Brobecker <brobecker@adacore.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tromey@adacore.com>,
Pedro Alves via Gdb-patches <gdb-patches@sourceware.org>,
Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH 2/3] Consistently use BFD's time
Date: Fri, 14 Aug 2020 16:40:03 -0700 [thread overview]
Message-ID: <20200814234003.GA27502@adacore.com> (raw)
In-Reply-To: <ba765596-e02c-6f4a-afb7-781a17e427a1@suse.de>
> > Pedro> Can you clarify what do you see not work? I tried rebasing it
> > Pedro> here, and it seems to work. It builds cleanly on GNU/Linux and
> > Pedro> mingw32-w64 (both -m64 and -m32). I've pasted the resulting patch below.
> >
> > What if we apply this patch, but also apply a patch to our gnulib to
> > avoid the timezone offsetting? We kept the code in
> > gnulib/update-gnulib.sh to make this pretty easy to do, and we could try
> > to work with upstream gnulib to make this feature optional (hopefully
> > eliminating the need for our patch).
> >
> > This would avoid the mtime comparison problem. I don't know how to
> > solve that another way, at least not without changing BFD to also use
> > gnulib -- which seems to come with its own risks.
> >
> > Once we solve this somehow, I can rebase and update the original series
> > here.
> >
> > This is one of the final blockers to the 10.1 branch, so it would be
> > good to reach some kind of resolution soon.
> >
>
> Hi,
>
> [ it's been a bit more that two weeks since the last email on this, so
> I'm pinging this. ]
>
> Joel wrote as summary here (
> https://sourceware.org/pipermail/gdb-patches/2020-August/171176.html ) :
> ...
> Hannes proposed, as a workaround, a hack involving
> undefining/redefining the fstat macro. The way it was proposed
> is not stricly portable as I understand it (it uses an extension),
> so we wouldn't be able to use it as is. But I'm starting to
> warm to the idea of doing something like that on the branch,
> while we take the time we need to discuss the proper approach.
> ...
>
> Is there any indication by now which way we want to go with this for the
> 10.1 branch?
For the short-term solution, I think the best compromise is to patch
gnulib like Tom suggests. We have the infrastructure to do that and
maintain the patch for as long as it takes to discuss the proper
solution (personally, I think the only way forward for the better
solution will require a live discussion; I am happy to help set that
up if people would find it useful).
Please let us know if you guys think there is a better short term
solution. Otherwise, let's ask Tom to submit a patch that patches
gnulib, and start creating the GDB 10 pre-release.
--
Joel
next prev parent reply other threads:[~2020-08-14 23:40 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 21:10 [PATCH 0/3] Fix gdb's BFD cache Tom Tromey
2020-01-14 21:10 ` [PATCH 2/3] Consistently use BFD's time Tom Tromey
2020-01-14 23:17 ` Christian Biesinger via gdb-patches
2020-01-15 17:51 ` Eli Zaretskii
2020-01-16 20:47 ` Pedro Alves
2020-01-16 21:58 ` Christian Biesinger via gdb-patches
2020-01-16 22:31 ` Pedro Alves
2020-01-17 8:48 ` Eli Zaretskii
2020-01-17 18:32 ` Tom Tromey
2020-01-17 21:03 ` Tom Tromey
2020-01-18 11:07 ` Eli Zaretskii
2020-01-20 15:52 ` Pedro Alves
2020-01-20 15:53 ` Pedro Alves
2020-01-20 20:50 ` Eli Zaretskii
2020-01-20 20:58 ` Pedro Alves
2020-01-21 15:50 ` Pedro Alves
2020-01-21 19:38 ` Eli Zaretskii
2020-01-21 17:56 ` Eli Zaretskii
2020-01-23 22:05 ` Tom Tromey
2020-06-19 17:51 ` Tom Tromey
2020-04-01 20:20 ` Tom Tromey
2020-06-18 14:14 ` Tom Tromey
2020-06-18 15:04 ` Eli Zaretskii
2020-06-18 16:00 ` Tom Tromey
2020-06-18 17:27 ` Eli Zaretskii
2020-06-18 17:32 ` Pedro Alves
2020-06-18 17:54 ` Eli Zaretskii
2020-06-19 12:02 ` Pedro Alves
2020-06-19 12:13 ` Eli Zaretskii
2020-06-19 17:09 ` Tom Tromey
2020-06-19 20:24 ` Tom Tromey
2020-06-19 23:05 ` Pedro Alves
2020-07-21 19:39 ` Tom Tromey
2020-07-28 19:31 ` Tom Tromey
2020-08-13 12:15 ` Tom de Vries
2020-08-14 23:40 ` Joel Brobecker [this message]
2020-08-23 16:09 ` Joel Brobecker
2020-08-23 23:32 ` Pedro Alves
2020-08-24 20:04 ` Joel Brobecker
2020-09-02 14:45 ` Tom Tromey
2020-09-02 14:59 ` Joel Brobecker
2020-06-18 17:57 ` Tom Tromey
2020-01-14 21:10 ` [PATCH 1/3] Avoid hash table corruption in gdb_bfd.c Tom Tromey
2020-01-14 22:26 ` Christian Biesinger via gdb-patches
2020-01-14 22:13 ` [PATCH 3/3] Further simplify gdb BFD caching Tom Tromey
2020-01-23 22:30 ` Tom Tromey
2020-09-02 18:45 ` Tom Tromey
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=20200814234003.GA27502@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tdevries@suse.de \
--cc=tromey@adacore.com \
/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