Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stanshebs@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Paul_Koning@dell.com, gdb <gdb@sourceware.org>
Subject: Re: GDB on Mac OS
Date: Wed, 12 Aug 2015 15:35:00 -0000	[thread overview]
Message-ID: <CA+5-Q5LP4OGfCxViL_jDAY2ryR5ie6-EaD0ehekQoO_O+JLocA@mail.gmail.com> (raw)
In-Reply-To: <20150812151419.GM22225@adacore.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


      reply	other threads:[~2015-08-12 15:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12  0:15 Paul_Koning
     [not found] ` <20150812031208.GJ22225@adacore.com>
2015-08-12 13:38   ` Paul_Koning
2015-08-12 13:53     ` Jonas Maebe
2015-08-12 13:59     ` Joel Brobecker
2015-08-12 14:06       ` Paul_Koning
2015-08-12 15:14         ` Joel Brobecker
2015-08-12 15:35           ` Stan Shebs [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=CA+5-Q5LP4OGfCxViL_jDAY2ryR5ie6-EaD0ehekQoO_O+JLocA@mail.gmail.com \
    --to=stanshebs@google.com \
    --cc=Paul_Koning@dell.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@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