This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH 1/3] Fix mismatched struct vs class tags.

From: John Baldwin <jhb at freebsd dot org>
To: Pedro Alves <palves at redhat dot com>
Cc: Simon Marchi <simon dot marchi at polymtl dot ca>, gdb-patches at sourceware dot org
Date: Thu, 24 Nov 2016 11:15:01 -0800
Subject: Re: [PATCH 1/3] Fix mismatched struct vs class tags.
Authentication-results: sourceware.org; auth=none
References: <20161123200652.89209-1-jhb@FreeBSD.org> <5282476.671uSJnE6M@ralph.baldwin.cx> <1f8967dd-3a56-8c1e-6ad2-b47b101e90ec@redhat.com>

On Thursday, November 24, 2016 06:50:30 PM Pedro Alves wrote:
> On 11/24/2016 05:45 PM, John Baldwin wrote:
> 
> > Ok.  At the moment we don't have a clang-specific warning set, but if we
> > add one we can add this to that.
> 
> We likely don't need one.  Our infrustruture checks whether a
> warning works before enabling it.  See gdb/warning.m4.

Hmmm.  The only odd case I can think of is -Wunused-function.  Right now
clang triggers warnings when VEC() is used, so ideally -Wunused-function
would only be present for GCC and not for clang.  I can look at adding
other -Wno-foo warnings for clang things we wish to ignore however.

-- 
John Baldwin

Follow-Ups:
- Re: [PATCH 1/3] Fix mismatched struct vs class tags.
  - From: Pedro Alves

References:
- [PATCH 0/3] Fix various C++ related clang warnings
  - From: John Baldwin
- Re: [PATCH 1/3] Fix mismatched struct vs class tags.
  - From: John Baldwin
- Re: [PATCH 1/3] Fix mismatched struct vs class tags.
  - From: Pedro Alves

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]