https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64835
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2015-02-11
CC| |jamborm at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot
gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Jambor <jamborm at gcc dot gnu.org> ---
The problem is that in the testcase iinline-1.c as it is in the
testsuite, we use -fno-ipa-cp on the command line so that the
interprocedural phase of IPA-CP is not run so that it does not
interfere with the interprocedural stage of inlining, which however
uses information gathered by the function body analysis of ipa-prop
(which is invoked by both IPA-CP and inlining). However, when we
inspect the function specific optimizations in ipa-prop at this stage,
we bail out if we see -fno-ipa-cp.
So yes, there is a clear inconsistency, but at the same time, having
the ability to switch off only the interprocedural part of IPA-CP is
extremely convenient for testing how the inliner uses jump functions
and other stuff gathered by ipa-prop. I'll try to come up with some
fix.
