Re: Avoid unnnecesary copying of ipa-prop's expressions

2014-02-10 Thread Richard Biener
On Fri, 7 Feb 2014, Jan Hubicka wrote: > > On Thu, 6 Feb 2014, Jan Hubicka wrote: > > > > > Hi, > > > at WPA we currently read trees accessed by jump functions and then copy > > > them > > > to remove location that is already known to be UNKNOWN and then keep > > > copying > > > them for every

Re: Avoid unnnecesary copying of ipa-prop's expressions

2014-02-07 Thread Jan Hubicka
> On Thu, 6 Feb 2014, Jan Hubicka wrote: > > > Hi, > > at WPA we currently read trees accessed by jump functions and then copy them > > to remove location that is already known to be UNKNOWN and then keep copying > > them for every inline clone introduced (and there are many for firefox) > > > >

Re: Avoid unnnecesary copying of ipa-prop's expressions

2014-02-07 Thread Richard Biener
On Thu, 6 Feb 2014, Jan Hubicka wrote: > Hi, > at WPA we currently read trees accessed by jump functions and then copy them > to remove location that is already known to be UNKNOWN and then keep copying > them for every inline clone introduced (and there are many for firefox) > > This patch makes

Avoid unnnecesary copying of ipa-prop's expressions

2014-02-06 Thread Jan Hubicka
Hi, at WPA we currently read trees accessed by jump functions and then copy them to remove location that is already known to be UNKNOWN and then keep copying them for every inline clone introduced (and there are many for firefox) This patch makes us to copy only when expression really has an locat