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 tree-optimization/23835] case where gcc 4.1.0 -O3 compile takes two times longer than gcc 3.4.3
Date: Tue, 13 Sep 2005 23:14:00 -0000 [thread overview]
Message-ID: <20050913231317.2825.qmail@sourceware.org> (raw)
In-Reply-To: <20050912163013.23835.jaffe@broad.mit.edu>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-13 23:13 -------
We have at least 50000 SSA_NAMEs, that is just huge. We have only V_MAY_DEFs for .GLOBAL_VAR and
a TMT.
This happens on all targets and not just ia64.
--
What |Removed |Added
----------------------------------------------------------------------------
GCC build triplet|ia64-unknown-linux-gnu |
GCC host triplet|ia64-unknown-linux-gnu |
GCC target triplet|ia64-unknown-linux-gnu |
Summary|case where gcc 4.1.0 -O3 |case where gcc 4.1.0 -O3
|compile takes two times |compile takes two times
|longer than gcc 3.4.3, on |longer than gcc 3.4.3
|ia64 |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23835
next prev parent reply other threads:[~2005-09-13 23:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 16:30 [Bug c++/23835] New: case where gcc 4.1.0 -O3 compile takes 4 times longer than gcc 3.4.3, on ia64 jaffe at broad dot mit dot edu
2005-09-12 16:32 ` [Bug c++/23835] " pinskia at gcc dot gnu dot org
2005-09-12 16:34 ` jaffe at broad dot mit dot edu
2005-09-12 18:35 ` pinskia at gcc dot gnu dot org
2005-09-13 22:03 ` jaffe at broad dot mit dot edu
2005-09-13 22:09 ` pinskia at gcc dot gnu dot org
2005-09-13 22:18 ` [Bug tree-optimization/23835] " pinskia at gcc dot gnu dot org
2005-09-13 22:38 ` pinskia at gcc dot gnu dot org
2005-09-13 23:14 ` pinskia at gcc dot gnu dot org [this message]
2005-09-13 23:29 ` [Bug tree-optimization/23835] case where gcc 4.1.0 -O3 compile takes two times longer than gcc 3.4.3 pinskia at gcc dot gnu dot org
2005-09-14 0:32 ` pinskia at gcc dot gnu dot org
2005-09-14 0:35 ` [Bug tree-optimization/23835] [4.1 Regression] case where gcc 4.1.0 -O3 compile takes two times longer than gcc 3.4.3 and 4.0.0 pinskia at gcc dot gnu dot org
2005-09-14 0:42 ` pinskia at gcc dot gnu dot org
2005-09-14 2:50 ` dberlin at gcc dot gnu dot org
2005-09-15 1:28 ` [Bug tree-optimization/23835] [4.1 Regression] case where gcc 4.1.0 -O3 compile takes two times longer earlier versions cvs-commit at gcc dot gnu dot org
2005-09-15 16:40 ` pinskia at gcc dot gnu dot org
2005-09-15 16:49 ` pinskia at gcc dot gnu dot org
2005-09-15 16:50 ` pinskia at gcc dot gnu dot org
2005-09-28 9:46 ` jaffe at broad dot mit 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=20050913231317.2825.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).