This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: GDB on Mac OS
- From: Stan Shebs <stanshebs at google dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Paul_Koning at dell dot com, gdb <gdb at sourceware dot org>
- Date: Wed, 12 Aug 2015 10:35:00 -0500
- Subject: Re: GDB on Mac OS
- Authentication-results: sourceware.org; auth=none
- References: <1739A299-ACE9-4D7F-A1DF-E64C89ECC8D1 at dell dot com> <20150812031208 dot GJ22225 at adacore dot com> <95D02D49-26D2-454E-8E11-70EBF7CB5EC5 at dell dot com> <20150812135946 dot GL22225 at adacore dot com> <024F3741-3957-4893-8932-506F53002A26 at dell dot com> <20150812151419 dot GM22225 at adacore dot com>
On Wed, Aug 12, 2015 at 10:14 AM, Joel Brobecker <brobecker@adacore.com> wrote:
>> Does that apply to LLVM warnings, too? There are a whole lot of
>> those. Some are caused by sending GCC options to the compiler that
>> LLVM doesnât understand, in spite of the fact that it proclaims itself
>> as GCC. It seems that configure will need to be able to tell the
>> difference and avoid triggering those LLVM incompatibilities.
>
> I'm not sure about LLVM. I *think* that we're only aiming for
> warning-free with GCC.
In practice, LLVM (more specifically Clang) has been including more
and more GCC flags, just because everybody wants warning-free and
nobody wants configure-hell. :-)
Clang warnings have been catching cases that GCC misses (quite a few
in the Google codebase, in fact), so it seems worthwhile to collect
and check those, at least periodically.
Stan