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 rtl-optimization/59802] excessive compile time in RTL optimizers (loop unswitching, CPROP)
Date: Tue, 14 Jan 2014 11:20:00 -0000	[thread overview]
Message-ID: <bug-59802-4-GqaG1vJg8C@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59802-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59802

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |compile-time-hog
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-01-14
          Component|c                           |rtl-optimization
            Summary|excessive compile time in   |excessive compile time in
                   |loop unswitching            |RTL optimizers (loop
                   |                            |unswitching, CPROP)
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 4.8 shows

 CPROP                   :  45.00 (57%) usr   0.02 ( 4%) sys  45.01 (57%) wall 
  4016 kB ( 2%) ggc
 TOTAL                 :  78.48             0.57            79.04            
213705 kB

while GCC 4.9 has

 loop invariant motion   :  10.11 (11%) usr   0.01 ( 2%) sys  10.16 (11%) wall 
     2 kB ( 0%) ggc
 loop unswitching        :   9.81 (11%) usr   0.00 ( 0%) sys   9.83 (11%) wall 
     1 kB ( 0%) ggc
 CPROP                   :  48.16 (54%) usr   0.04 ( 7%) sys  48.20 (54%) wall 
  4444 kB ( 2%) ggc

so I can't really confirm the unswitching slowness (this is r205857 which
is somewhat older than your test).

Generally I think we should probably consider removing RTL unswitching,
there is not a single loop unswitched by RTL for this testcase.


  reply	other threads:[~2014-01-14 11:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14  8:49 [Bug c/59802] New: excessive compile time in loop unswitching dcb314 at hotmail dot com
2014-01-14 11:20 ` rguenth at gcc dot gnu.org [this message]
2014-01-14 11:21 ` [Bug rtl-optimization/59802] excessive compile time in RTL optimizers (loop unswitching, CPROP) rguenth at gcc dot gnu.org
2014-01-14 12:04 ` dcb314 at hotmail dot com
2014-01-14 13:24 ` rguenth at gcc dot gnu.org
2014-01-14 13:54 ` rguenth at gcc dot gnu.org
2014-01-15 12:17 ` rguenth at gcc dot gnu.org
2014-01-19 21:28 ` dcb314 at hotmail dot com

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-59802-4-GqaG1vJg8C@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: link
Be 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).