This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 0/5] Remove a few hurdles of compiling with clang
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Simon Marchi <simon dot marchi at ericsson dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sun, 11 Jun 2017 05:36:35 +0300
- Subject: Re: [PATCH 0/5] Remove a few hurdles of compiling with clang
- Authentication-results: sourceware.org; auth=none
- References: <1497124689-11842-1-git-send-email-simon.marchi@ericsson.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Simon Marchi <simon.marchi@ericsson.com>
> CC: Simon Marchi <simon.marchi@ericsson.com>
> Date: Sat, 10 Jun 2017 21:58:04 +0200
>
> 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
Question to Joel and Pedro: Do we really want to go to these length to
accommodate clang? What's our policy?