On 03/05/08 09:14, Richard Guenther wrote:
I agree, still it is probably nice to be able to compare testcase behavior
with/without SFTs with the same state of trunk for a while. So I'd just
adjust the default of --para max-fields-for-field-sensitive for now
(after the oracle patches got in) and
On Wed, 5 Mar 2008, Diego Novillo wrote:
> On 03/05/08 06:48, Richard Guenther wrote:
>
> > you can see that in both cases the runs without SFTs are significantly
> > better(!) Which hints at the fact that we do a poor job with parititoning
> > and/or that partitioning triggers earlier with SFTs
On 03/05/08 06:48, Richard Guenther wrote:
you can see that in both cases the runs without SFTs are significantly
better(!) Which hints at the fact that we do a poor job with parititoning
and/or that partitioning triggers earlier with SFTs enabled.
All these differences seem to be less than 1
Here are SPEC CPU 2000 results with plain trunk and the two alias-oracle
patches. Base results are plain -O3 -ffast-math, peak results include
--param max-fields-for-field-sensitive=0 which effectively disables the
creation of SFTs.
Unpatched (three runs):
E
