From: Tom Tromey <tom@tromey.com>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/2 gdb] Fix --enable-libctf, --disable-static, and tests sans CTF-capable toolchain
Date: Tue, 15 Oct 2019 20:02:00 -0000 [thread overview]
Message-ID: <87zhi1ok0n.fsf@tromey.com> (raw)
In-Reply-To: <20191009182648.274292-2-nick.alcock@oracle.com> (Nick Alcock's message of "Wed, 9 Oct 2019 19:26:48 +0100")
>>>>> "Nick" == Nick Alcock <nick.alcock@oracle.com> writes:
Thanks for doing this. This looks basically ok, just a few nits below.
The patch should have some intro text. gdb style is to use the same
text for the description in the email and for the commit.
Nick> +if test x${enable_static} = xno; then
Nick> + LIBCTF="-Wl,--rpath,../libctf/.libs ../libctf/.libs/libctf.so"
Indentation of 2 here...
Nick> +if test "${enable_libctf}" = yes; then
Nick> + AC_DEFINE(ENABLE_LIBCTF, 1, [Handle .ctf type-info sections])
... but 4 here. I think they could be the same, whatever is most common
in the file, or most common nearby anyhow.
Nick> +#else
Nick> +
Nick> +void
Nick> +_initialize_ctfread (void)
gdb just uses "()", not "(void)" now.
Nick> diff --git a/gdb/testsuite/configure.ac b/gdb/testsuite/configure.ac
...
Nick> +AC_ARG_ENABLE(libctf,
Nick> +[AS_HELP_STRING([--enable-libctf], [Handle .ctf type-info sections])], [
This seems to be identical to what's in gdb.
I don't really mind, but if you're duplicating this across several
subdirectories, it may be better to stick a new macro into a new .m4 in
config/, then use that everywhere.
Nick> +if {[skip_ctf_tests]} {
Nick> + return
Nick> +}
I think these spots should call "unsupported" to explain what happened.
Nick> +proc skip_ctf_tests {} {
I suspect you probably want to use gdb_caching_proc here. This can be
friendlier when running a lot of parallel tests, because it caches the
result, and this proc is doing a compilation.
Tom
next prev parent reply other threads:[~2019-10-15 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 18:27 [PATCH v2 1/2] binutils, ld: work with --disable-libctf Nick Alcock
2019-10-09 18:27 ` [PATCH v2 2/2 gdb] Fix --enable-libctf, --disable-static, and tests sans CTF-capable toolchain Nick Alcock
2019-10-15 20:02 ` Tom Tromey [this message]
2019-10-16 12:53 ` Nick Alcock
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=87zhi1ok0n.fsf@tromey.com \
--to=tom@tromey.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=nick.alcock@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).