From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, ludo@gnu.org,
sandra@codesourcery.com, tom@tromey.com
Subject: Re: GDB 10 branching - 2020-07-18 Update
Date: Tue, 21 Jul 2020 14:38:45 -0600 [thread overview]
Message-ID: <87o8o8eh7u.fsf@tromey.com> (raw)
In-Reply-To: <20200718194522.GA32708@adacore.com> (Joel Brobecker's message of "Sat, 18 Jul 2020 12:45:22 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
Joel> * [TomT/HannesD] <PR win32/25302>
Joel> Mismatching fstat() function calls in gdb_bfd_open() and cache_bstat()
Joel> https://sourceware.org/bugzilla/show_bug.cgi?id=25302
Joel> Latest discussion at:
Joel> https://sourceware.org/pipermail/gdb-patches/2020-June/169670.html
Joel> Tom said he hasn't had time to look at Pedro's reply, unfortunately.
Joel> I'm not super confident that he'll have much time soon either.
Joel> Should we start looking at Plan B?
I don't know what to do about this one.
I'd like to add https://sourceware.org/bugzilla/show_bug.cgi?id=26197 to
the list. This is a rust regression that came from the variant part
rewrite. I was able to reproduce it with the official rust 1.12, which
is especially disappointing because the only reason I even have that
installed was to test this code.
Tom
next prev parent reply other threads:[~2020-07-21 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 19:45 Joel Brobecker
2020-07-19 2:28 ` Eli Zaretskii
2020-07-19 15:03 ` Joel Brobecker
2020-07-25 7:56 ` Eli Zaretskii
2020-07-20 11:34 ` Rainer Orth
2020-07-20 15:22 ` Joel Brobecker
2020-07-21 20:38 ` Tom Tromey [this message]
2020-07-22 12:57 ` Joel Brobecker
2020-07-22 20:32 ` Kevin Buettner
2020-07-23 18:43 ` Joel Brobecker
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=87o8o8eh7u.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ludo@gnu.org \
--cc=sandra@codesourcery.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