Hi Jeff,
On 23 Jun 2016, at 4:21 AM, Jeff Law wrote:
>
> OK for the trunk. Please install.
>
> Sorry for the delays.
>
> Jeff
I might not have the access rights to commit to trunk.
Best regards
- Marcel
From: Andi Kleen
autofdo create_gcov creates an extra .imports file. Always remove that
too when running an autofdo test case.
gcc/testsuite/:
* 2016-06-26 Andi Kleen
* lib/profopt.exp (profopt-execute): Remove .imports files.
---
gcc/testsuite/lib/profopt.exp | 1 +
1 file changed
From: Andi Kleen
This fixes some basic issues with the profile test cases with autofdo.
- Disable checking for value transformations that autofdo does not
support.
- Disable checking for fixed hit counts which autofdo does not support
- Enable dumping of afdo log file and check right log file.
From: Andi Kleen
not just when verbose. This ensures all command lines needed to
reproduce the test case are always logged
gcc/testsuite/:
* 2016-06-26 Andi Kleen
* lib/profopt.exp (profopt-execute): Always log profiler
command line.
---
gcc/testsuite/lib/profopt.exp | 2 +-
From: Andi Kleen
Print some information about indirect call promotions in the afdo dump
file. Do it in the same format as the instrumented profiler so that
the test suite can match on it.
gcc/:
2016-06-26 Andi Kleen
* auto-profile.c (update_inlined_ind_target,
afdo_indirect_
From: Andi Kleen
Autofdo outputs to different dump files and doesn't support some
transformation that normal profiling. Add dg-final-scan-autofdo
and dg-final-scan-not-autofdo statements to the test suite
so that the test cases can hande those cases separately.
gcc/testsuite/:
2016-06-26 Andi
This fixes some of the problems with profile test cases running with autofdo
There are still remaining failures that need to be addressed, but this is the
low hanging fruit.
-Andi
From: Andi Kleen
The pass to transform gimple based on value profiling runs with autofdo
on, but currently every transformation fails. For indirect calls autofdo
does it on its own, and it doesn't suppport other value profiling. So don't
run this pass when autofdo is active. This also avoids bogu
Hello!
As shown by listed PRs, the spill-to-vector regs infrastructure is not
yet ready. And with no fix in sight, I have disabled it for x86
altogether.
2016-06-26 Uros Bizjak
PR target/70902
PR target/71453
PR target/71555
PR target/71596
PR target/71
Hi,
this patch further tune the branch prediction in recursive functions.
The loop predictor now check if the loop body contains a recursive call and
use different predictors in that case. This makes it possible to specify
that loops contianing self recursive calls usually iterate fewer time.
Boo
While working on the last patch to pa.c, I realized that it was possible to
optimize indirect calls
in various situations. In particular, a long PIC call to $$dyncall takes 5
instructions, and $$dyncall
is 8 instructions on hpux and 6 instructions on linux.
It is possible to do optimized inline
On Sun, 26 Jun 2016, H.J. Lu wrote:
> On Sun, Jun 26, 2016 at 12:49 AM, Alexander Monakov
> wrote:
> > On Sat, 25 Jun 2016, H.J. Lu wrote:
> >> The resolver for ifunc functions might resolve to a non-local function.
> >
> > I think the explanation doesn't match the testcase, in which all three
>
On Sun, Jun 26, 2016 at 12:49 AM, Alexander Monakov wrote:
> On Sat, 25 Jun 2016, H.J. Lu wrote:
>> The resolver for ifunc functions might resolve to a non-local function.
>
> I think the explanation doesn't match the testcase, in which all three
> functions: the resolver, the symbol being resolve
On Sat, 25 Jun 2016, H.J. Lu wrote:
> The resolver for ifunc functions might resolve to a non-local function.
I think the explanation doesn't match the testcase, in which all three
functions: the resolver, the symbol being resolved, and the ultimate
resolution are all static. I don't think there w
14 matches
Mail list logo
