public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lucier at math dot purdue dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37567]  New: tree SSA to normal checking takes abnormally long time
Date: Wed, 17 Sep 2008 22:58:00 -0000	[thread overview]
Message-ID: <bug-37567-271@http.gcc.gnu.org/bugzilla/> (raw)

When configured with

Configured with: ../../mainline/configure --with-gmp=/pkgs/gmp-4.2.2/
--with-mpfr=/pkgs/gmp-4.2.2/ --prefix=/pkgs/gcc-mainline
--enable-gather-detailed-mem-stats

and run on the testcase of PR 26854 with

/pkgs/gcc-mainline/bin/gcc -Wall -W -Wno-unused -O1 -fno-math-errno
-fschedule-insns2 -fno-trapping-math -fno-strict-aliasing -fwrapv
-fomit-frame-pointer -fPIC -ftime-report -fmem-report -c all.i >>&
mainline-stats-2008-09-17-c

one line stands out:

 tree SSA to normal    : 485.81 (61%) usr   0.12 ( 0%) sys 486.01 (59%) wall  
93945 kB (12%) ggc
 TOTAL                 : 793.99            24.78           819.45            
795105 kB

without checking, this is

 tree SSA to normal    :  13.31 ( 8%) usr   0.10 ( 1%) sys  13.42 ( 7%) wall  
93945 kB (12%) ggc
 TOTAL                 : 168.33            14.57           183.12            
794201 kB

The timings of other parts of a checking-enabled compiler seem reasonable.


-- 
           Summary: tree SSA to normal checking takes abnormally long time
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: lucier at math dot purdue dot edu
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


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


             reply	other threads:[~2008-09-17 22:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 22:58 lucier at math dot purdue dot edu [this message]
2008-09-18  8:51 ` [Bug middle-end/37567] " rguenth at gcc dot gnu dot org
2008-09-18 20:02 ` amacleod at redhat dot com
2008-09-18 20:09 ` lucier at math dot purdue dot edu
2008-09-18 20:11 ` lucier at math dot purdue dot edu
2008-09-18 20:20 ` amacleod at redhat dot com
2008-09-18 20:24 ` amacleod at redhat dot com
2008-09-18 20:29 ` lucier at math dot purdue dot edu
2008-09-19  8:37 ` rguenth at gcc dot gnu dot org
2008-09-19 13:28 ` amacleod at redhat dot com
2008-09-19 17:39 ` amacleod at gcc dot gnu dot org
2008-09-26 15:35 ` lucier at math dot purdue dot edu

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-37567-271@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).