[cfe-dev] Debugging Information; exploiting comments

Ted Kremenek kremenek at apple.com
Fri Nov 9 16:57:01 PST 2007


Hi Cedric,

This is really a separate thread, so I'm forwarding this to the cfe- 
dev list.

Everyone: please feel free to chime in.

Begin forwarded message:

> I am investigating adding debugging information to clang. Do you  
> think it to
> soon? (I would like to add a -g flag to the drivers and add  
> conditional llvm
> debug intrinsic emission in CodeGen).
> Do you have already some idea on the question? (I studied llvm-gcc  
> debug
> generation and would add something similar)
>
> Another idea I had is implementing a documentation tools (like  
> doxygen)
> using clang. The problem is that the existing framework doesn't permit
> analyzing the commentary and parsing in the same pass (At least I  
> don't see
> how). I would need to add some sort of callback in the lexer or
> preprocesseur for processing the comment (we can't parse the comment  
> token,
> it would be an impossible task). The callback would store the  
> comment and
> when the next declaration would be parsed, the stored comment is  
> used for
> decoration the declaration. Do you think this is a good way? Another  
> way
> would be to add some sort of filter between the lexer and the parser  
> which
> would process and delete the comment token as they come, but it would
> probably be slower and on the critical path (not sure the lexing/ 
> parsing
> part is time critical since the semantical analysis will eventually  
> probably
> be a lot slower).




More information about the cfe-dev mailing list