On Tue, Sep 24, 2013 at 11:48 PM, MAYUR PANDEY <[email protected]> wrote:
> This is the similar way it has been fixed in gcc. They have kept a note > of parent and they break the loop when it is again noticed. With the usage > of global > > map there are no performance issues as such. Also please suggest the > alternate way of fixing this issue. > I'm not an expert on overload resolution rules, so if you're certain we actually need a map to catch this case, that's fine, I guess. (Richard, can you chime in?) The rest of my feedback still applies. -Eli ------- *Original Message* ------- > > *Sender* : Eli Friedman<[email protected]> > > *Date* : Sep 10, 2013 06:53 (GMT+09:00) > > *Title* : Re: Fix for ICE in clang due to infinite loop. > > > On Mon, Sep 9, 2013 at 5:08 AM, MAYUR PANDEY <[email protected]> wrote: > >> Hi, >> >> Attached is the fix for Compiler crash caused by infinite loop when we >> try to compile the following code. >> >> >> >> struct A; >> >> struct B >> { >> B (A const &); >> >> B (B &); >> }; >> >> struct A >> { >> A (B); >> }; >> >> B >> f (B const& b) >> { >> return b; >> >> } >> > >
_______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
