public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joern dot rennecke at superh-support dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/16266] [4.0 regression] gcc.dg/c99-intconst-1.c compilation is very slow
Date: Fri, 08 Oct 2004 23:11:00 -0000 [thread overview]
Message-ID: <20041008231146.31843.qmail@sourceware.org> (raw)
In-Reply-To: <20040629130803.16266.amylaar@gcc.gnu.org>
------- Additional Comments From joern dot rennecke at superh-support dot com 2004-10-08 23:11 -------
Subject: Re: [4.0 regression] gcc.dg/c99-intconst-1.c compilation is very slow
--- pinskia at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
> ------- Additional Comments From pinskia at gcc dot
> gnu dot org 2004-10-08 11:57 -------
> Since you did not configure with --disable-checking
> the time is expected to raise. See the note here:
> Extra diagnostic checks enabled; compiler may run
> slowly.
> Configure with --disable-checking to disable checks.
>
> Can you try with --disable-checking as requested
> before.
The pre-tree-ssa-merge compiler was also compiled with
checking enabled,
and the testcase took only eight seconds on the slower
processor.
That's a factor of sixteen, times the speed
differential of the processors.
Are you suggesting that
a) All or most of the speed regression comes from a
slowdown in
the --enable-checking code (or more of it)
and
b) We should keep regression tests viable by using --disable-checking?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16266
next prev parent reply other threads:[~2004-10-08 23:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 14:08 [Bug regression/16266] New: 3.5 regression: " amylaar at gcc dot gnu dot org
2004-06-29 14:34 ` [Bug regression/16266] [3.5 regression] " pinskia at gcc dot gnu dot org
2004-06-29 14:39 ` reichelt at gcc dot gnu dot org
2004-06-29 16:06 ` joern dot rennecke at superh dot com
2004-06-29 17:05 ` joern dot rennecke at superh dot com
2004-08-15 3:30 ` [Bug middle-end/16266] " pinskia at gcc dot gnu dot org
2004-10-06 23:19 ` [Bug middle-end/16266] [4.0 " giovannibajo at libero dot it
2004-10-07 6:44 ` amylaar at spamcop dot net
2004-10-07 6:48 ` echristo at redhat dot com
2004-10-08 9:17 ` amylaar at spamcop dot net
2004-10-08 11:57 ` pinskia at gcc dot gnu dot org
2004-10-08 23:11 ` joern dot rennecke at superh-support dot com [this message]
2004-10-08 23:32 ` Diego Novillo
2004-10-08 23:32 ` dnovillo at redhat dot com
2004-10-09 1:58 ` amylaar at spamcop dot net
2004-10-09 2:01 ` pinskia at gcc dot gnu dot org
2004-10-09 2:51 ` pinskia at gcc dot gnu dot org
2004-10-09 3:32 ` pinskia at gcc dot gnu dot org
2004-10-09 3:43 ` pinskia at gcc dot gnu dot org
2004-10-09 4:27 ` pinskia at gcc dot gnu dot org
2004-10-09 4:48 ` pinskia at gcc dot gnu dot org
2004-10-09 5:04 ` pinskia at gcc dot gnu dot org
2004-10-11 18:32 ` pinskia at gcc dot gnu dot org
2004-10-11 18:32 ` cvs-commit at gcc dot gnu dot org
2004-11-17 18:02 ` fjahanian at apple dot com
2004-11-17 18:14 ` pinskia at gcc dot gnu dot org
2004-11-17 18:17 ` pinskia 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=20041008231146.31843.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).