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 middle-end/39326] Segmentation fault with -O1, out of memory with -O2 Date: Fri, 17 Jan 2014 13:53:00 -0000 [thread overview] Message-ID: <bug-39326-4-33VxIw5lmk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-39326-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39326 --- Comment #54 from Richard Biener <rguenth at gcc dot gnu.org> --- For the original testcase on trunk we get at -O1 tree loop invariant motion: 37.20 (16%) usr 0.02 ( 1%) sys 37.20 (16%) wall 12127 kB ( 1%) ggc dead store elim1 : 17.42 ( 7%) usr 0.04 ( 2%) sys 17.44 ( 7%) wall 28345 kB ( 3%) ggc dead store elim2 : 26.22 (11%) usr 0.00 ( 0%) sys 26.20 (11%) wall 18664 kB ( 2%) ggc combiner : 15.36 ( 6%) usr 0.04 ( 2%) sys 15.39 ( 6%) wall 70073 kB ( 7%) ggc LRA hard reg assignment : 74.07 (31%) usr 0.02 ( 1%) sys 74.05 (31%) wall 0 kB ( 0%) ggc reload CSE regs : 12.67 ( 5%) usr 0.00 ( 0%) sys 12.66 ( 5%) wall 13315 kB ( 1%) ggc TOTAL : 237.86 1.83 239.60 999181 kB so that's still slow (memory usage is peaking at about 1.5GB now, during RA). tree LIM: Each sample counts as 0.01 seconds. % cumulative self self total time seconds seconds calls s/call s/call name 4.22 120.72 9.83 299080 0.00 0.00 ref_indep_loop_p_2(loop*, mem_ref*, bool) 1.89 151.82 4.41 1712943886 0.00 0.00 mem_refs_may_alias_p(mem _ref*, mem_ref*, pointer_map_t**) [clone .constprop.60] 0.21 197.02 0.48 12192 0.00 0.00 force_move_till(tree_node*, tree_node**, void*) at -O2 this will blow up completely as it then runs into the affine-based disambiguation.
next prev parent reply other threads:[~2014-01-17 13:53 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-39326-4@http.gcc.gnu.org/bugzilla/> 2013-03-06 11:08 ` steven at gcc dot gnu.org 2013-03-06 11:38 ` rguenth at gcc dot gnu.org 2013-03-06 16:50 ` sergstesh at yahoo dot com 2013-03-06 23:39 ` steven at gcc dot gnu.org 2013-03-07 0:08 ` steven at gcc dot gnu.org 2013-03-07 0:27 ` steven at gcc dot gnu.org 2013-03-07 8:10 ` steven at gcc dot gnu.org 2013-03-07 8:45 ` rguenther at suse dot de 2013-03-07 8:48 ` rguenther at suse dot de 2013-03-07 8:53 ` rguenther at suse dot de 2013-03-07 9:58 ` steven at gcc dot gnu.org 2013-03-07 10:14 ` sergstesh at yahoo dot com 2013-03-07 10:15 ` rguenther at suse dot de 2013-03-07 17:14 ` sergstesh at yahoo dot com 2013-03-07 17:31 ` steven at gcc dot gnu.org 2013-03-07 17:34 ` steven at gcc dot gnu.org 2013-03-07 21:48 ` sergstesh at yahoo dot com 2013-03-07 22:16 ` steven at gcc dot gnu.org 2013-03-07 23:19 ` steven at gcc dot gnu.org 2013-03-08 9:14 ` rguenth at gcc dot gnu.org 2013-03-08 9:14 ` rguenth at gcc dot gnu.org 2013-03-08 9:23 ` rguenther at suse dot de 2013-03-09 14:58 ` steven at gcc dot gnu.org 2013-03-09 17:26 ` steven at gcc dot gnu.org 2013-03-11 9:40 ` steven at gcc dot gnu.org 2013-03-12 10:47 ` rguenth at gcc dot gnu.org 2013-03-12 14:05 ` rguenth at gcc dot gnu.org 2013-03-15 16:07 ` rguenth at gcc dot gnu.org 2013-03-18 8:44 ` rguenth at gcc dot gnu.org 2013-03-21 20:04 ` jakub at gcc dot gnu.org 2013-03-22 14:01 ` rguenth at gcc dot gnu.org 2013-03-26 10:10 ` rguenth at gcc dot gnu.org 2014-01-15 15:14 ` rguenth at gcc dot gnu.org 2014-01-17 13:53 ` rguenth at gcc dot gnu.org [this message] 2022-03-10 15:05 ` rguenth at gcc dot gnu.org 2024-02-20 13:14 ` rguenth at gcc dot gnu.org 2009-02-28 15:23 [Bug c/39326] New: " sergstesh at yahoo dot com 2009-03-02 17:16 ` [Bug middle-end/39326] " pinskia at gcc dot gnu dot org 2009-03-03 13:36 ` sergstesh at yahoo dot com 2009-03-03 13:49 ` rguenther at suse dot de 2009-03-03 14:15 ` sergstesh at yahoo dot com 2009-03-17 11:05 ` rguenth at gcc dot gnu dot org 2009-03-17 12:42 ` rguenth at gcc dot gnu dot org 2009-03-17 12:59 ` rguenth at gcc dot gnu dot org 2009-03-17 13:10 ` rguenth at gcc dot gnu dot 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-39326-4-33VxIw5lmk@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).