This is the mail archive of the gcc-patches@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: Unreviewed patches (since February/March)


On Wed, Sep 11, 2002 at 10:59:17PM -0400, Daniel Berlin wrote:
> Note nothing about "entrance".
> It tells you what the behavior is like *during* the block in which it's 
> declared.

Hum.  I'd have sworn I remembered different language.

Nevertheless, we've no data flow whatsoever, so we can't
properly determine "based".

> > At this point, C does in fact conflict with both A and B.
> 
> No, it doesn't.
> It conflicts with exactly one of them, but we might not know which one.

Correct.  I was sloppy here, based on what gcc actually does.

> In fact, you could write an optimization that copied the rest of the 
> function into two arms of an if (p) block, and in each one, you'd be able 
> to optimize appropriately.

Correct.  It'd be hard to determine if that was worth while
though...


r~


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