public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/53787] Possible IPA-SRA / IPA-CP improvement Date: Fri, 23 May 2014 15:52:00 -0000 [thread overview] Message-ID: <bug-53787-4-ofhreXFmuB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53787-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53787 --- Comment #19 from Martin Jambor <jamborm at gcc dot gnu.org> --- Author: jamborm Date: Fri May 23 15:52:20 2014 New Revision: 210864 URL: http://gcc.gnu.org/viewcvs?rev=210864&root=gcc&view=rev Log: 2014-05-23 Martin Jambor <mjambor@suse.cz> PR tree-optimization/53787 * params.def (PARAM_IPA_MAX_AA_STEPS): New param. * ipa-prop.h (ipa_node_params): Rename uses_analysis_done to analysis_done, update all uses. * ipa-prop.c: Include domwalk.h (param_analysis_info): Removed. (param_aa_status): New type. (ipa_bb_info): Likewise. (func_body_info): Likewise. (ipa_get_bb_info): New function. (aa_overwalked): Likewise. (find_dominating_aa_status): Likewise. (parm_bb_aa_status_for_bb): Likewise. (parm_preserved_before_stmt_p): Changed to use new param AA info. (load_from_unmodified_param): Accept func_body_info as a parameter instead of parms_ainfo. (parm_ref_data_preserved_p): Changed to use new param AA info. (parm_ref_data_pass_through_p): Likewise. (ipa_load_from_parm_agg_1): Likewise. Update callers. (compute_complex_assign_jump_func): Changed to use new param AA info. (compute_complex_ancestor_jump_func): Likewise. (ipa_compute_jump_functions_for_edge): Likewise. (ipa_compute_jump_functions): Removed. (ipa_compute_jump_functions_for_bb): New function. (ipa_analyze_indirect_call_uses): Likewise, moved variable declarations down. (ipa_analyze_virtual_call_uses): Accept func_body_info instead of node and info, moved variable declarations down. (ipa_analyze_call_uses): Accept and pass on func_body_info instead of node and info. (ipa_analyze_stmt_uses): Likewise. (ipa_analyze_params_uses): Removed. (ipa_analyze_params_uses_in_bb): New function. (ipa_analyze_controlled_uses): Likewise. (free_ipa_bb_info): Likewise. (analysis_dom_walker): New class. (ipa_analyze_node): Handle node-specific forbidden analysis, initialize and free func_body_info, use dominator walker. (ipcp_modif_dom_walker): New class. (ipcp_transform_function): Create and free func_body_info, use ipcp_modif_dom_walker, moved a lot of functionality there. Modified: trunk/gcc/ChangeLog trunk/gcc/doc/invoke.texi trunk/gcc/ipa-prop.c trunk/gcc/ipa-prop.h trunk/gcc/params.def
prev parent reply other threads:[~2014-05-23 15:52 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-27 17:26 [Bug lto/53787] New: Possible lto improvement izamyatin at gmail dot com 2012-06-27 17:39 ` [Bug lto/53787] " dominiq at lps dot ens.fr 2012-06-27 17:57 ` izamyatin at gmail dot com 2012-06-27 20:03 ` hjl.tools at gmail dot com 2012-06-28 8:17 ` izamyatin at gmail dot com 2012-06-28 8:22 ` izamyatin at gmail dot com 2012-06-28 10:08 ` [Bug tree-optimization/53787] Possible IPA-SRA / IPA-CP improvement rguenth at gcc dot gnu.org 2012-07-19 19:10 ` izamyatin at gmail dot com 2012-07-20 19:59 ` jamborm at gcc dot gnu.org 2012-07-26 22:49 ` steven at gcc dot gnu.org 2012-07-27 9:35 ` jamborm at gcc dot gnu.org 2012-08-30 15:59 ` jamborm at gcc dot gnu.org 2012-11-07 15:56 ` jamborm at gcc dot gnu.org 2012-11-08 14:43 ` jamborm at gcc dot gnu.org 2013-01-22 15:32 ` ysrumyan at gmail dot com 2013-01-22 15:33 ` ysrumyan at gmail dot com 2013-01-25 18:33 ` jamborm at gcc dot gnu.org 2014-02-14 17:16 ` jamborm at gcc dot gnu.org 2014-02-28 14:26 ` izamyatin at gmail dot com 2014-05-23 15:52 ` jamborm at gcc dot gnu.org [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-53787-4-ofhreXFmuB@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).