[cfe-dev] Debug Info Generation in Clang.

[Sanjiv.Gupta at microchip.com]

> -----Original Message-----
> From: Chris Lattner [mailto:clattner at apple.com] 
> Sent: Tuesday, April 29, 2008 10:16 PM
> To: Sanjiv Kumar Gupta - I00171
> Cc: cedric.venet at laposte.net; cfe-dev at cs.uiuc.edu
> Subject: Re: [cfe-dev] Debug Info Generation in Clang.
> 
> On Apr 29, 2008, at 3:54 AM, Sanjiv.Gupta at microchip.com wrote:
> > I was thinking that putting it in CodeGenFunction::EmitStmt 
> may result 
> > in redundant stoppoint being emitted. But that is taken care of by 
> > EmitStopPoint function itself, which checks to see if we 
> have changed 
> > from the previous line number. So EmitStmt looks the correct place.
> 
> Yep, that makes sense to me too.
> 

Well, putting it into EmitStmt still results into unnecessay stoppoints
being generated.

For a piece of code like
 1: foo ()
 2: {
 3:   int I = 5;
 4: }

Two stoppoints will be generated for line 2 and line 3;

We do not want to generate a stoppoint for a '{' (CompoundStmt).


I am thinking to go back to my earlier thoughts and put it into below
functions:
 EmitScalarExpr
 EmitComplexExpr
 EmitAggExpr

- Sanjiv