This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: [RFC] GCC caret diagnostics

From: "Manuel López-Ibáñez" <lopezibanez at gmail dot com>
To: "Chris Lattner" <clattner at apple dot com>
Cc: "Ian Lance Taylor" <iant at google dot com>, tromey at redhat dot com, "GCC Mailing List" <gcc at gcc dot gnu dot org>
Date: Thu, 13 Mar 2008 01:07:47 +0100
Subject: Re: [RFC] GCC caret diagnostics
References: <6c33472e0803021226o7d30c1b5rb811db0591cb4086@mail.gmail.com> <m3r6em4jij.fsf@fleche.redhat.com> <m3fxv2ezpo.fsf@google.com> <A88C5C30-C9B5-4FEA-84EB-6EB91716FE64@apple.com>

On 08/03/2008, Chris Lattner <clattner@apple.com> wrote:
>
> clang points into the original input buffer that was lexed from.  This
>  requires keeping the original files mapped into the address space of
>  the compiler.  However, clang only produces diagnostics from the front-
>  end, not from the middle-end.

So no warnings for uninitialized variables?

Cheers,

Manuel.

Follow-Ups:
- Re: [RFC] GCC caret diagnostics
  - From: Chris Lattner

References:
- [RFC] GCC caret diagnostics
  - From: Manuel López-Ibáñez
- Re: [RFC] GCC caret diagnostics
  - From: Tom Tromey
- Re: [RFC] GCC caret diagnostics
  - From: Ian Lance Taylor
- Re: [RFC] GCC caret diagnostics
  - From: Chris Lattner

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