public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/44563] GCC uses a lot of RAM when compiling a large numbers of functions Date: Fri, 13 Mar 2015 08:47:00 -0000 [thread overview] Message-ID: <bug-44563-4-eMmTSPwVDh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44563-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44563 --- Comment #31 from Richard Biener <rguenth at gcc dot gnu.org> --- Author: rguenth Date: Fri Mar 13 08:47:14 2015 New Revision: 221409 URL: https://gcc.gnu.org/viewcvs?rev=221409&root=gcc&view=rev Log: 2015-03-10 Richard Biener <rguenther@suse.de> PR middle-end/44563 * tree-cfgcleanup.c (split_bb_on_noreturn_calls): Remove. (cleanup_tree_cfg_1): Do not call it. (execute_cleanup_cfg_post_optimizing): Fixup the CFG here. (fixup_noreturn_call): Mark the stmt as control altering. * tree-cfg.c (execute_fixup_cfg): Do not dump the function here. (pass_data_fixup_cfg): Produce a dump file. * tree-ssa-dom.c: Include tree-cfgcleanup.h. (need_noreturn_fixup): New global. (pass_dominator::execute): Fixup queued noreturn calls. (optimize_stmt): Queue calls that became noreturn for fixup. * tree-ssa-forwprop.c (pass_forwprop::execute): Likewise. * tree-ssa-pre.c: Include tree-cfgcleanup.h. (el_to_fixup): New global. (eliminate_dom_walker::before_dom_childre): Queue calls that became noreturn for fixup. (eliminate): Fixup queued noreturn calls. * tree-ssa-propagate.c: Include tree-cfgcleanup.h. (substitute_and_fold_dom_walker): New member stmts_to_fixup. (substitute_and_fold_dom_walker::before_dom_children): Queue alls that became noreturn for fixup. (substitute_and_fold): Fixup queued noreturn calls. Modified: trunk/gcc/ChangeLog trunk/gcc/tree-cfg.c trunk/gcc/tree-cfgcleanup.c trunk/gcc/tree-ssa-dom.c trunk/gcc/tree-ssa-forwprop.c trunk/gcc/tree-ssa-pre.c trunk/gcc/tree-ssa-propagate.c
next prev parent reply other threads:[~2015-03-13 8:47 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44563-4@http.gcc.gnu.org/bugzilla/> 2010-12-12 23:55 ` [Bug tree-optimization/44563] " hubicka at gcc dot gnu.org 2010-12-13 0:58 ` hubicka at gcc dot gnu.org 2010-12-13 1:00 ` hubicka at gcc dot gnu.org 2010-12-13 1:07 ` hubicka at gcc dot gnu.org 2010-12-13 1:17 ` hubicka at gcc dot gnu.org 2010-12-13 1:47 ` hubicka at gcc dot gnu.org 2010-12-13 13:22 ` hubicka at gcc dot gnu.org 2010-12-17 0:08 ` hubicka at gcc dot gnu.org 2015-03-07 0:22 ` hubicka at gcc dot gnu.org 2015-03-09 9:36 ` rguenth at gcc dot gnu.org 2015-03-09 11:33 ` rguenth at gcc dot gnu.org 2015-03-09 15:26 ` rguenth at gcc dot gnu.org 2015-03-09 15:36 ` rguenth at gcc dot gnu.org 2015-03-10 4:55 ` hubicka at ucw dot cz 2015-03-10 8:26 ` rguenth at gcc dot gnu.org 2015-03-10 8:35 ` rguenther at suse dot de 2015-03-10 11:54 ` rguenth at gcc dot gnu.org 2015-03-10 12:03 ` rguenth at gcc dot gnu.org 2015-03-10 12:31 ` jakub at gcc dot gnu.org 2015-03-10 12:44 ` rguenth at gcc dot gnu.org 2015-03-10 12:51 ` rguenther at suse dot de 2015-03-10 13:19 ` rguenth at gcc dot gnu.org 2015-03-12 15:09 ` rguenth at gcc dot gnu.org 2015-03-13 8:43 ` [Bug ipa/44563] " rguenth at gcc dot gnu.org 2015-03-13 8:47 ` rguenth at gcc dot gnu.org [this message] 2015-03-13 8:53 ` rguenth at gcc dot gnu.org 2015-03-13 8:55 ` rguenth at gcc dot gnu.org 2015-03-16 0:07 ` hubicka at ucw dot cz 2024-02-16 13:52 ` rguenth at gcc dot gnu.org
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-44563-4-eMmTSPwVDh@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).