public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot 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: Tue, 17 Mar 2009 12:42:00 -0000	[thread overview]
Message-ID: <20090317124219.3425.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39326-13529@http.gcc.gnu.org/bugzilla/>



------- Comment #18 from rguenth at gcc dot gnu dot org  2009-03-17 12:42 -------
Vlad, for the second testcase I see

-O0:

 expand                :   0.78 (19%) usr   0.04 ( 5%) sys   0.83 (16%) wall  
44335 kB (49%) ggc
 integrated RA         :   1.05 (25%) usr   0.03 ( 4%) sys   1.13 (22%) wall   
1036 kB ( 1%) ggc
 reload                :   0.55 (13%) usr   0.02 ( 3%) sys   0.59 (12%) wall   
3585 kB ( 4%) ggc

-O1:

 integrated RA         :  73.95 (77%) usr   1.18 (50%) sys  76.20 (76%) wall   
2898 kB ( 3%) ggc

(on alias improvements branch I see
 combiner              :  24.89 (17%) usr   0.51 (28%) sys  25.41 (17%) wall 
448053 kB (82%) ggc
 integrated RA         :  69.81 (47%) usr   0.36 (20%) sys  70.22 (46%) wall   
3212 kB ( 1%) ggc
as tree loop invariant motion does lots of stuff there)

-O2:

 PRE                   :  25.49 (26%) usr   0.03 ( 3%) sys  25.52 (26%) wall   
3513 kB ( 3%) ggc
 integrated RA         :  36.98 (38%) usr   0.24 (21%) sys  37.31 (38%) wall   
2158 kB ( 2%) ggc


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vmakarov at gcc dot gnu dot
                   |                            |org


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


  parent reply	other threads:[~2009-03-17 12:42 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-28 15:23 [Bug c/39326] New: " sergstesh at yahoo dot com
2009-02-28 15:29 ` [Bug c/39326] " sergstesh at yahoo dot com
2009-02-28 15:32 ` sergstesh at yahoo dot com
2009-02-28 15:34 ` sergstesh at yahoo dot com
2009-02-28 17:23 ` sergstesh at yahoo dot com
2009-02-28 17:57 ` rguenth at gcc dot gnu dot org
2009-02-28 18:00 ` rguenth at gcc dot gnu dot org
2009-02-28 18:10 ` rguenth at gcc dot gnu dot org
2009-03-01  3:04 ` sergstesh at yahoo dot com
2009-03-01  3:06 ` sergstesh at yahoo dot com
2009-03-01  3:09 ` sergstesh at yahoo dot com
2009-03-01  3:54 ` sergstesh at yahoo dot com
2009-03-01 11:39 ` rguenth at gcc dot gnu dot org
2009-03-02 17:01 ` rguenth at gcc dot gnu dot org
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 [this message]
2009-03-17 12:59 ` rguenth at gcc dot gnu dot org
2009-03-17 13:10 ` rguenth at gcc dot gnu dot org
     [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
2022-03-10 15:05 ` rguenth at gcc dot gnu.org
2024-02-20 13:14 ` 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=20090317124219.3425.qmail@sourceware.org \
    --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).