From: Tom Tromey <tom@tromey.com>
To: Gary Benson via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [OB PATCH] Build two gdb.cp testcases with -Wno-unused-comparison
Date: Fri, 29 May 2020 12:08:12 -0600 [thread overview]
Message-ID: <87mu5qaa2b.fsf@tromey.com> (raw)
In-Reply-To: <1590757423-18004-1-git-send-email-gbenson@redhat.com> (Gary Benson via Gdb-patches's message of "Fri, 29 May 2020 14:03:43 +0100")
>>>>> "Gary" == Gary Benson via Gdb-patches <gdb-patches@sourceware.org> writes:
Gary> +if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile} \
Gary> + {debug c++ additional_flags=-Wno-unused-comparison}] } {
Won't this cause build (and therefore test) failures if the compiler
does not accept this option?
I wonder if there's a way to fix the warning in the C++ source file
instead.
Tom
next prev parent reply other threads:[~2020-05-29 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 13:03 Gary Benson
2020-05-29 18:08 ` Tom Tromey [this message]
2020-05-29 18:31 ` Pedro Alves
2020-06-16 12:42 ` Gary Benson
2020-06-16 15:11 ` Pedro Alves
2020-06-17 17:29 ` Gary Benson
2020-06-17 19:53 ` [PATCH] W/ Clang, compile C/C++ testcases with -Wno-unknown-warning-option Pedro Alves
2020-06-18 16:18 ` Gary Benson
2020-06-24 22:26 ` Pedro Alves
2020-07-02 10:02 ` Gary Benson
2020-06-16 12:38 ` [OB PATCH] Build two gdb.cp testcases with -Wno-unused-comparison Gary Benson
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=87mu5qaa2b.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/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