From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [patch+8.0] release branch: Fix: --enable-werror
Date: Sat, 22 Apr 2017 16:20:00 -0000 [thread overview]
Message-ID: <87y3usv2h5.fsf@redhat.com> (raw)
In-Reply-To: <20170421085204.GA5501@host1.jankratochvil.net> (Jan Kratochvil's message of "Fri, 21 Apr 2017 10:52:04 +0200")
On Friday, April 21 2017, Jan Kratochvil wrote:
> Hi,
>
> gdb-8.0-branch
> ./configure --enable-werror --enable-targets=all
> aarch64-tdep.c:3045:13: error: ‘void selftests::aarch64_process_record_test()’ declared ‘static’ but never defined [-Werror=unused-function]
> arm-tdep.c:9601:13: error: ‘void selftests::arm_record_test()’ declared ‘static’ but never defined [-Werror=unused-function]
>
> OK for check-in?
>
> Please do not tell me release branches do not support --enable-werror as this
> is due to a sourcebase bug, not due to some unexpected compiler
> incompatibility.
>
> Sergio: Shouldn't it be also buildbot-tested?
Yes, it should. We have an Arch64 builder managed by Yao. It should
be possible to set up builders for the 8.0 branch.
> Jan
>
> gdb/ChangeLog
> 2017-04-21 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * aarch64-tdep.c (selftests::aarch64_process_record_test): Make it #if
> GDB_SELF_TEST.
> * arm-tdep.c (selftests::arm_record_test): Likewise.
>
> diff --git a/gdb/aarch64-tdep.c b/gdb/aarch64-tdep.c
> index 28c2573..6113621 100644
> --- a/gdb/aarch64-tdep.c
> +++ b/gdb/aarch64-tdep.c
> @@ -3040,10 +3040,12 @@ aarch64_dump_tdep (struct gdbarch *gdbarch, struct ui_file *file)
> paddress (gdbarch, tdep->lowest_pc));
> }
>
> +#if GDB_SELF_TEST
> namespace selftests
> {
> static void aarch64_process_record_test (void);
> }
> +#endif
>
> /* Suppress warning from -Wmissing-prototypes. */
> extern initialize_file_ftype _initialize_aarch64_tdep;
> diff --git a/gdb/arm-tdep.c b/gdb/arm-tdep.c
> index c8fabfb..9ac667f 100644
> --- a/gdb/arm-tdep.c
> +++ b/gdb/arm-tdep.c
> @@ -9596,10 +9596,12 @@ arm_dump_tdep (struct gdbarch *gdbarch, struct ui_file *file)
> (unsigned long) tdep->lowest_pc);
> }
>
> +#if GDB_SELF_TEST
> namespace selftests
> {
> static void arm_record_test (void);
> }
> +#endif
>
> extern initialize_file_ftype _initialize_arm_tdep; /* -Wmissing-prototypes */
>
>
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2017-04-22 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 8:52 Jan Kratochvil
2017-04-21 14:04 ` Pedro Alves
2017-04-21 14:18 ` [commit+8.0] " Jan Kratochvil
2017-04-22 16:20 ` Sergio Durigan Junior [this message]
2017-04-22 16:34 ` Jan Kratochvil
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=87y3usv2h5.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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