From: Simon Marchi <simon.marchi@polymtl.ca>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/5] Remove a few hurdles of compiling with clang
Date: Sat, 17 Jun 2017 21:23:00 -0000 [thread overview]
Message-ID: <0cac219c61a95a84c76e6c78b9465f7e@polymtl.ca> (raw)
In-Reply-To: <1497124689-11842-1-git-send-email-simon.marchi@ericsson.com>
On 2017-06-10 21:58, Simon Marchi wrote:
> It is currently possible to build with clang by jumping through a few
> hoops and
> compiling without -Werror, but it is not pretty. There is a _ton_ of
> warnings.
> clang often gives some good and relevant warnings (e.g. [1]), so it
> would be
> useful to get the number to a reasonnable level to be able to see those
> that
> are actually relevant. I started to work on the lowest hanging fruits
> and the
> changes that should not be too controversial.
>
> [1] https://sourceware.org/ml/gdb-patches/2017-06/msg00252.html
>
> Simon Marchi (5):
> gdb: Pass -x c++ to the compiler
> gdb: Use -Werror when checking for (un)supported warning flags
> gdb: Add -Wno-mismatched-tags
> linux-low: Remove usage of "register" keyword
> Add ATTRIBUTE_PRINTF to trace_start_error
>
> gdb/Makefile.in | 2 +-
> gdb/configure | 7 ++++---
> gdb/gdbserver/Makefile.in | 2 +-
> gdb/gdbserver/configure | 13 +++++++------
> gdb/gdbserver/linux-low.c | 16 ++++++++--------
> gdb/nat/fork-inferior.h | 2 +-
> gdb/warning.m4 | 7 ++++---
> 7 files changed, 26 insertions(+), 23 deletions(-)
This is now pushed in.
Simon
prev parent reply other threads:[~2017-06-17 21:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-10 19:58 Simon Marchi
2017-06-10 19:58 ` [PATCH 3/5] gdb: Add -Wno-mismatched-tags Simon Marchi
2017-06-10 19:58 ` [PATCH 2/5] gdb: Use -Werror when checking for (un)supported warning flags Simon Marchi
2017-06-10 19:58 ` [PATCH 1/5] gdb: Pass -x c++ to the compiler Simon Marchi
2017-06-10 19:58 ` [PATCH 5/5] Add ATTRIBUTE_PRINTF to trace_start_error Simon Marchi
2017-06-14 19:49 ` Sergio Durigan Junior
2017-06-10 19:58 ` [PATCH 4/5] linux-low: Remove usage of "register" keyword Simon Marchi
2017-06-11 2:36 ` [PATCH 0/5] Remove a few hurdles of compiling with clang Eli Zaretskii
2017-06-12 7:56 ` Yao Qi
2017-06-12 14:36 ` Eli Zaretskii
2017-06-12 15:54 ` Simon Marchi
2017-06-12 16:23 ` Andrew Pinski
2017-06-12 16:35 ` Pedro Alves
2017-06-12 16:37 ` Andrew Pinski
2017-06-12 16:45 ` Pedro Alves
2017-06-12 16:55 ` Pedro Alves
2017-06-12 16:44 ` Simon Marchi
2017-06-12 16:55 ` Andrew Pinski
2017-06-12 17:00 ` Simon Marchi
2017-06-12 16:44 ` Eli Zaretskii
2017-06-13 9:14 ` Yao Qi
2017-06-13 10:23 ` Simon Marchi
2017-06-13 11:06 ` Pedro Alves
2017-06-13 11:08 ` Simon Marchi
2017-06-13 14:38 ` Eli Zaretskii
2017-06-13 17:07 ` Simon Marchi
2017-06-13 19:23 ` Eli Zaretskii
2017-06-13 20:17 ` Simon Marchi
2017-06-14 2:29 ` Eli Zaretskii
2017-06-14 10:45 ` Pedro Alves
2017-06-16 16:12 ` John Baldwin
2017-06-13 15:22 ` Yao Qi
2017-06-13 15:44 ` Eli Zaretskii
2017-06-14 9:07 ` Yao Qi
2017-06-19 8:07 ` Yao Qi
2017-06-13 10:44 ` Pedro Alves
2017-06-13 15:09 ` Joel Brobecker
2017-06-17 21:23 ` Simon Marchi [this message]
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=0cac219c61a95a84c76e6c78b9465f7e@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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).