From: Simon Marchi <simon.marchi@ericsson.com>
To: <gdb-patches@sourceware.org>
Cc: Simon Marchi <simon.marchi@ericsson.com>
Subject: [PATCH 0/3] Third series towards a warning-less clang build
Date: Sun, 25 Jun 2017 17:45:00 -0000 [thread overview]
Message-ID: <1498412703-24303-1-git-send-email-simon.marchi@ericsson.com> (raw)
This series fixes a few last issues we get when building with clang and
-Werror. It was not as bad as I expected (especially the vec.h warnings).
Combined with this patch:
https://sourceware.org/ml/gdb-patches/2017-06/msg00252.html
gdb itself builds cleanly with clang and -Werror (not the rest of the
binutils-gdb repo yet through).
Simon Marchi (3):
ada-lex: Ignore warnings about register keyword
vec: Silence -Wunused-function warnings on clang
record-full: Remove unused function netorder16
gdb/ada-lex.l | 9 +++++++++
gdb/common/diagnostics.h | 6 ++++++
gdb/common/vec.h | 11 +++++++++++
gdb/record-full.c | 10 ----------
4 files changed, 26 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2017-06-25 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 17:45 Simon Marchi [this message]
2017-06-25 17:45 ` [PATCH 3/3] record-full: Remove unused function netorder16 Simon Marchi
2017-06-26 10:43 ` Yao Qi
2017-06-26 14:54 ` Simon Marchi
2017-06-25 17:45 ` [PATCH 1/3] ada-lex: Ignore warnings about register keyword Simon Marchi
2017-06-26 13:13 ` Pedro Alves
2017-06-26 13:39 ` Simon Marchi
2017-06-26 14:54 ` [pushed] " Simon Marchi
2017-06-25 17:45 ` [PATCH 2/3] vec: Silence -Wunused-function warnings on clang Simon Marchi
2017-06-26 9:28 ` Pedro Alves
2017-06-26 12:28 ` Simon Marchi
2017-06-26 12:47 ` Pedro Alves
2017-06-26 12:52 ` Simon Marchi
[not found] ` <1498481156-10705-1-git-send-email-simon.marchi@ericsson.com>
2017-06-26 13:03 ` [PATCH 2/3 v2] " Pedro Alves
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=1498412703-24303-1-git-send-email-simon.marchi@ericsson.com \
--to=simon.marchi@ericsson.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