public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/23490] [3.4/4.0/4.1 Regression] Long compile time for array initializer with inlined constructor
Date: Sat, 20 Aug 2005 02:29:00 -0000	[thread overview]
Message-ID: <20050820022631.28539.qmail@sourceware.org> (raw)
In-Reply-To: <20050819224516.23490.falk@debian.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-08-20 02:26 -------
earth:~>time gcc -O1 t.cc -S
5.993u 0.056s 0:06.18 97.7%     0+0k 0+0io 0pf+0w
earth:~>time gcc -O1 t.cc -S -O2
11.529u 0.058s 0:11.84 97.7%    0+0k 0+0io 0pf+0w
earth:~>time gcc t.cc -S 
0.426u 0.012s 0:00.93 46.2%     0+0k 0+0io 0pf+0w

This is without checking disable.

Interesting 2.95.3 does not have the issue even with -fstrict-aliasing:
earth:~>time ~/ia32_linux_gcc2_95/bin/gcc t.cc -S
0.248u 0.019s 0:00.51 49.0%     0+0k 0+0io 0pf+0w
earth:~>time ~/ia32_linux_gcc2_95/bin/gcc t.cc -S -O1
1.259u 0.013s 0:01.63 77.3%     0+0k 0+0io 0pf+0w
earth:~>time ~/ia32_linux_gcc2_95/bin/gcc t.cc -S -O2
1.630u 0.021s 0:01.90 86.8%     0+0k 0+0io 0pf+0w
earth:~>time ~/ia32_linux_gcc2_95/bin/gcc t.cc -S -O2 -fstrict-aliasing
1.626u 0.018s 0:01.81 90.0%     0+0k 0+0io 0pf+0w

This has been a bug since 3.0.4.

It also happens on x86 too.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
  GCC build triplet|alphaev68-unknown-linux-gnu |
   GCC host triplet|alphaev68-unknown-linux-gnu |
 GCC target triplet|alphaev68-unknown-linux-gnu |
      Known to fail|                            |3.0.4 3.3.3 3.4.0 4.0.0
      Known to work|                            |2.95.3
   Last reconfirmed|0000-00-00 00:00:00         |2005-08-20 02:26:31
               date|                            |
            Summary|Long compile time for array |[3.4/4.0/4.1 Regression]
                   |initializer with inlined    |Long compile time for array
                   |constructor                 |initializer with inlined
                   |                            |constructor
   Target Milestone|---                         |4.0.2


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


  parent reply	other threads:[~2005-08-20  2:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 22:48 [Bug tree-optimization/23490] New: " falk at debian dot org
2005-08-19 23:03 ` [Bug rtl-optimization/23490] " pinskia at gcc dot gnu dot org
2005-08-19 23:27 ` pinskia at gcc dot gnu dot org
2005-08-20  2:29 ` pinskia at gcc dot gnu dot org [this message]
2005-09-19  0:02 ` [Bug rtl-optimization/23490] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-09-19  0:05 ` pinskia at gcc dot gnu dot org
2005-09-19  0:07 ` steven at gcc dot gnu dot org
2005-09-19 11:07 ` steven at gcc dot gnu dot org
2005-09-27 16:15 ` mmitchel at gcc dot gnu dot org
     [not found] <bug-23490-2744@http.gcc.gnu.org/bugzilla/>
2005-10-31  5:17 ` mmitchel at gcc dot gnu dot org
2005-11-03 20:06 ` hubicka at gcc dot gnu dot org
2005-11-03 20:20 ` falk at debian dot org
2005-11-03 21:23 ` hubicka at ucw dot cz
2005-11-05  0:55 ` hubicka 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=20050820022631.28539.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).