diff options
author | Jan Hubicka <hubicka@ucw.cz> | 2025-09-03 17:55:54 +0200 |
---|---|---|
committer | Jan Hubicka <hubicka@ucw.cz> | 2025-09-03 17:56:22 +0200 |
commit | 2c4fcab25fc0362359c87ab955b24c54aa41b46c (patch) | |
tree | e2fe444c9a71258cc8008234c76461c0c58de259 /libjava/classpath/gnu/java | |
parent | 2b8256d0ce18ed4d00868c78f5128d32884ccfa1 (diff) | |
download | gcc-2c4fcab25fc0362359c87ab955b24c54aa41b46c.zip gcc-2c4fcab25fc0362359c87ab955b24c54aa41b46c.tar.gz gcc-2c4fcab25fc0362359c87ab955b24c54aa41b46c.tar.bz2 |
Do not auto-enable loop optimizations with AutoFDO
With -O2 we automatically enable several loop optimizations with -fprofile-use.
The rationale is that those optimizations at -O3 only mainly since they may
hurt performance or not pay back in code size when used blindly on all loops.
Profile feedback gives us data on number of iterations which is used by heuristics
controlling those optimizations.
Currently auto-FDO is not that good on determining number of iterations so I think we
do not want to enable them until we can prove that those are useful.
This is affecting primarily -O2 codegen.
Theoretically auto-FdO with lbr can be pretty good on estimating # of
iterations, but to make it useful we will need to implement multiplicity for
discriminators at least.
Bootstrapped/regtested x86_64-linux, comitted.
gcc/ChangeLog:
* opts.cc (enable_fdo_optimizations): Do not auto-enabele loop
optimizations with AutoFDO.
Diffstat (limited to 'libjava/classpath/gnu/java')
0 files changed, 0 insertions, 0 deletions