Hi,
On Wed, Dec 21, 2011 at 05:29:51PM +0100, Jan Hubicka wrote:
Hi,
given that we already have a workaround for zero size increase
estimates from estimate_ipcp_clone_size_and_time, I see little reason
not to extend it to negative values too, 0 is really just as bad as -2
On Wed, Dec 21, 2011 at 5:29 PM, Jan Hubicka hubi...@ucw.cz wrote:
Hi,
given that we already have a workaround for zero size increase
estimates from estimate_ipcp_clone_size_and_time, I see little reason
not to extend it to negative values too, 0 is really just as bad as -2
that we are
On Wed, Dec 21, 2011 at 5:29 PM, Jan Hubicka hubi...@ucw.cz wrote:
Hi,
given that we already have a workaround for zero size increase
estimates from estimate_ipcp_clone_size_and_time, I see little reason
not to extend it to negative values too, 0 is really just as bad as -2
that we
2011/12/22 Jan Hubicka hubi...@ucw.cz:
On Wed, Dec 21, 2011 at 5:29 PM, Jan Hubicka hubi...@ucw.cz wrote:
Hi,
given that we already have a workaround for zero size increase
estimates from estimate_ipcp_clone_size_and_time, I see little reason
not to extend it to negative values too, 0
Hi,
On Wed, Dec 21, 2011 at 05:29:51PM +0100, Jan Hubicka wrote:
Hi,
given that we already have a workaround for zero size increase
estimates from estimate_ipcp_clone_size_and_time, I see little reason
not to extend it to negative values too, 0 is really just as bad as -2
that we are
Hi,
given that we already have a workaround for zero size increase
estimates from estimate_ipcp_clone_size_and_time, I see little reason
not to extend it to negative values too, 0 is really just as bad as -2
that we are getting in the testcase. Hopefully this will allow peple
who hit this bug
Hi,
given that we already have a workaround for zero size increase
estimates from estimate_ipcp_clone_size_and_time, I see little reason
not to extend it to negative values too, 0 is really just as bad as -2
that we are getting in the testcase. Hopefully this will allow peple
who hit this