public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenther at suse dot de" <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, 08 Mar 2013 09:23:00 -0000 [thread overview] Message-ID: <bug-39326-4-7Qsf4gW9kL@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 #42 from rguenther at suse dot de <rguenther at suse dot de> 2013-03-08 09:22:39 UTC --- On Thu, 7 Mar 2013, steven at gcc dot gnu.org wrote: > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39326 > > --- Comment #38 from Steven Bosscher <steven at gcc dot gnu.org> 2013-03-07 22:15:39 UTC --- > Created attachment 29612 > --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29612 > Punt on loops with more memory references than LIM can handle > > For the LIM problem, I'm thinking of a patch like this one (not tested > yet). Basically, this means giving up on really large loops with many > loads and/or stores. That's not an unreasonable thing to do anyway. > Code motion from really big loops usually isn't an improvement. > > Richi, could you have a look at this, and see if I've got it all right, > more-or-less? LIM is quite complicated and I'm not sure if I should > look at, or update, the set of optimizable loops somewhere. Yeah, well - it should be easy to avoid most overhead (even collecting the memory references) with my proposed scheme (see patch). First, for each BB count the number of memory stmts (easy, look for VUSEs), then, when walking the set of outermost loops we want to apply LIM to sum over its BB counts and instead walk over its siblings if the number is too large. But yes, limiting it should be done as it performs O(n^2) dependence checks (well, O(#of stores * #of memory references), so for a low number of stores it's quite cheap). I've yet to recover the obstack-ification of struct depend, struct mem_ref, struct mem_ref_locs and lim_aux_data allocations ... (LIM is the biggest load on malloc/free). > With the patch, and with "-O2 -fgcse", I now have: > > gap_TlnLv4.c: In function 'RDFT_49152_1': > gap_TlnLv4.c:37502:18: warning: -ftree-loop-im: number of memory references in > loop exceeds the --param loops-max-datarefs-for-datadeps threshold > [-Wdisabled-optimization] > t12308[500] = t12304[6144*i0+1000]; > ^ > > dead store elim1 : 57.70 ( 8%) > dead store elim2 : 76.82 (10%) > combiner : 360.07 (48%) > reload CSE regs : 55.44 ( 7%) > TOTAL : 743.77 Nice. Well ... ;)
next prev parent reply other threads:[~2013-03-08 9:23 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 [this message] 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 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-7Qsf4gW9kL@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).