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: Plugin that parse tree

From: Tom Tromey <tromey at redhat dot com>
To: Ian Lance Taylor <iant at google dot com>
Cc: Daniel MarjamÃki <daniel dot marjamaki at gmail dot com>, piervit at pvittet dot com, gcc at gcc dot gnu dot org
Date: Thu, 27 Jan 2011 12:36:17 -0700
Subject: Re: Plugin that parse tree
References: <ed10e8adfd7ebb41d2f361b2a06c2e11@localhost> <95f62d57256fbc424a68e891a679b390@localhost> <AANLkTi=WqRt4hOYs79dNe3_t67iC5xWDqTdx_5xPP3Mu@mail.gmail.com> <mcr8vya9u9h.fsf@google.com>

>>>>> "Ian" == Ian Lance Taylor <iant@google.com> writes:

Ian> The problem with warnings for this kind of code in C/C++ is that it
Ian> often arises in macro expansions.  I think it would be necessary to
Ian> first develop a scheme which lets us determine whether code resulted
Ian> from a macro expansion or not, which I think would be quite useful in a
Ian> number of different cases.

There is a patch series pending for this.

See the thread "Tracking locations of tokens resulting from macro
expansion".

Tom

Follow-Ups:
- Re: Plugin that parse tree
  - From: Daniel Marjamäki

References:
- Re: Plugin that parse tree
  - From: piervit
- Re: Plugin that parse tree
  - From: Daniel Marjamäki
- Re: Plugin that parse tree
  - From: Ian Lance Taylor

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