From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tromey@adacore.com>
Cc: Simon Marchi <simark@simark.ca>,
Joel Brobecker <brobecker@adacore.com>,
Wadud Miah <wadud.miah@nag.co.uk>,
"gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: building GDB 9.0.50.20191206
Date: Sun, 15 Dec 2019 16:17:00 -0000 [thread overview]
Message-ID: <87h821ef6w.fsf@tromey.com> (raw)
In-Reply-To: <871rt7vme9.fsf@tromey.com> (Tom Tromey's message of "Fri, 13 Dec 2019 16:25:18 -0700")
Tom> Review here:
Tom> https://sourceware.org/ml/gdb-patches/2019-08/msg00433.html
Tom> Maybe some comments there still need to be addressed. I can't recall
Tom> offhand.
I've updated my patch and re-read the thread.
The remaining issue is that I still haven't decided what to do about
<config.h> in files like nat/linux-btrace.c. The message referred to
above outlines the various approaches and their problems pretty well.
Tom
next prev parent reply other threads:[~2019-12-15 16:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 10:47 Wadud Miah
2019-12-12 14:10 ` Joel Brobecker
2019-12-12 14:22 ` Wadud Miah
2019-12-13 19:53 ` Simon Marchi
2019-12-13 20:01 ` Tom Tromey
2019-12-13 20:21 ` Simon Marchi
2019-12-13 23:25 ` Tom Tromey
2019-12-15 16:17 ` Tom Tromey [this message]
2019-12-17 6:01 ` Joel Brobecker
2019-12-18 20:23 ` Tom Tromey
2019-12-14 17:29 ` Christian Biesinger via gdb
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=87h821ef6w.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=simark@simark.ca \
--cc=tromey@adacore.com \
--cc=wadud.miah@nag.co.uk \
/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