https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121704
Mikael Pettersson <mikpelinux at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpelinux at gmail dot com
--- Comment #2 from Mikael Pettersson <mikpelinux at gmail dot com> ---
My git bisect says it started with r14-1909-g5a1ef1cfac0053:
5a1ef1cfac005370d0a5a0f85798724cb2c9cf5e is the first new commit
commit 5a1ef1cfac005370d0a5a0f85798724cb2c9cf5e (HEAD)
Author: Honza <[email protected]>
Date: Sun Jun 18 18:58:26 2023 +0200
Analyze SRA candidates in ipa-fnsummary
this patch extends ipa-fnsummary to anticipate statements that will be
removed
by SRA. This is done by looking for calls passing addresses of automatic
variables. In function body we look for dereferences from pointers of such
variables and mark them with new not_sra_candidate condition.
This is just first step which is overly optimistic. We do not try to prove
that
given automatic variable will not be SRAed even after inlining. We now
also
optimistically assume that the transformation will always happen. I will
restrict
this in a followup patch, but I think it is useful to gether some data on
how
much code is affected by this.
This is motivated by PR109849 where we fail to fully inline push_back.
The patch alone does not solve the problem even for -O3, but improves
analysis in this case.
gcc/ChangeLog:
PR tree-optimization/109849
