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: Ian Lance Taylor <iant at google dot com>
To: Kevin AndrÃ <hyperquantum at gmail 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: Tue, 25 Jan 2011 06:51:24 -0800
Subject: Re: Plugin that parse tree
References: <ed10e8adfd7ebb41d2f361b2a06c2e11@localhost> <95f62d57256fbc424a68e891a679b390@localhost> <AANLkTi=WqRt4hOYs79dNe3_t67iC5xWDqTdx_5xPP3Mu@mail.gmail.com> <mcr8vya9u9h.fsf@google.com> <AANLkTi=W+Y-NpqBhDnG4eK1qYOYgwSYAaVtcScr5oL54@mail.gmail.com>

Kevin AndrÃ <hyperquantum@gmail.com> writes:

> Is that ever going to be fixed? If a front end mangles its AST
> representation, then it cannot be used for static analysis.
>
> Even if the constant folding in the front end is necessary for
> checking semantics, you could still keep the original source in the
> AST and simply attach the result of constant folding as some sort of
> tag to the expression node.

I agree that it would be nice if this were fixed.  Like many things in
the free software world, it will happen if somebody volunteers to do it.
I don't think it is a priority for any of the active gcc developers.

Ian

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
- Re: Plugin that parse tree
  - From: Kevin AndrÃ

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