This is the mail archive of the
mailing list for the GCC project.
Re: Do not use PARM_DECLs in ipa-cp and ipa-prop
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: Richard Biener <richard dot guenther at gmail dot com>
- Cc: Jan Hubicka <hubicka at ucw dot cz>, gcc-patches at gcc dot gnu dot org, mjambor at suse dot cz
- Date: Thu, 1 Aug 2013 17:16:50 +0200
- Subject: Re: Do not use PARM_DECLs in ipa-cp and ipa-prop
- References: <20130801131135 dot GB22179 at kam dot mff dot cuni dot cz> <d77eab88-ee66-41ea-baf1-190898d9364f at email dot android dot com>
> Jan Hubicka <firstname.lastname@example.org> wrote:
> >this is preparation work to move DECL_ARGUMENTS and DECL_RESULT into
> >sections during WPA. Even with some work to release unused ones, there
> >are 4M
> >of PARM_DECLs and 2M of RESULT_DECLs streamed during LTO (for 6M of
> >function_decls) making them one of the most common nodes.
> >This patch makes ipa-cp and ipa-prop to not use DECL_ARGUMENTS during
> >stage. this only needed to tamn debug info, move logic doing casts
> >get_replacement_map to tree_function_versioning and stream move_cost
> >that is
> >computed form parm type.
> >Martin, does this patch look OK?
> What about uses in jump functions, like &parm? Are those sufficiently non-treeish already?
I do not think those can appear in jump functions - it is not IP invariant.
passthrough and friends are non-treeish.