public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "andre dot maute at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/16613] [3.4 Regression] compile time regression, when adding cerr usage
Date: Sat, 11 Dec 2004 03:28:00 -0000 [thread overview]
Message-ID: <20041211032837.28282.qmail@sourceware.org> (raw)
In-Reply-To: <20040718101108.16613.andre.maute@gmx.de>
------- Additional Comments From andre dot maute at gmx dot de 2004-12-11 03:28 -------
now with --disable-checking in the configure parameters for gcc-4.0
> g++-4.0-20041205-1-dc -v
Reading specs
from /opt/gcc-4.0-20041205-1-dc/lib/gcc/i686-pc-linux-gnu/4.0.0/specs
Configured with: ../gcc-4.0-20041205/configure
--prefix=/opt/gcc-4.0-20041205-1-dc --enable-shared --enable-languages=c,c++
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--disable-nls --program-suffix=-4.0-20041205-1-dc --with-arch=pentium3
--disable-checking
Thread model: posix
gcc version 4.0.0 20041205 (experimental)
> time g++-4.0-20041205-1-dc -c -O3 -D __NDEBUG__ compiletimetest2.cc
real 0m18.300s user 0m18.050s sys 0m0.250s
> time g++-4.0-20041205-1-dc -c -O3 -D __DEBUG__ compiletimetest2.cc
real 0m21.368s user 0m20.960s sys 0m0.440s
this looks much better but not as good as with g++-3.3.5
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16613
next prev parent reply other threads:[~2004-12-11 3:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 10:11 [Bug c++/16613] New: " andre dot maute at gmx dot de
2004-07-19 8:37 ` [Bug rtl-optimization/16613] [3.4/3.5? Regression] " pinskia at gcc dot gnu dot org
2004-07-19 14:00 ` bangerth at dealii dot org
2004-07-27 18:10 ` wilson at gcc dot gnu dot org
2004-08-29 18:47 ` mmitchel at gcc dot gnu dot org
2004-09-28 13:30 ` [Bug rtl-optimization/16613] [3.4/4.0? " pinskia at gcc dot gnu dot org
2004-11-01 0:46 ` mmitchel at gcc dot gnu dot org
2004-11-28 5:27 ` [Bug rtl-optimization/16613] [3.4 " lerdsuwa at gcc dot gnu dot org
2004-12-01 13:39 ` ebotcazou at gcc dot gnu dot org
2004-12-10 22:36 ` andre dot maute at gmx dot de
2004-12-10 22:43 ` andre dot maute at gmx dot de
2004-12-10 23:12 ` dberlin at gcc dot gnu dot org
2004-12-11 3:28 ` andre dot maute at gmx dot de [this message]
2004-12-11 8:10 ` pinskia at gcc dot gnu dot org
2005-05-01 23:42 ` [Bug rtl-optimization/16613] [3.4/4.0 " andre dot maute at gmx dot de
2005-05-05 20:12 ` andre dot maute at gmx dot de
2005-05-19 17:46 ` mmitchel at gcc dot gnu dot org
2005-07-22 21:16 ` pinskia at gcc dot gnu dot org
2005-08-09 20:52 ` rth at gcc dot gnu dot org
2005-09-27 16:23 ` mmitchel at gcc dot gnu dot org
-- strict thread matches above, loose matches on Subject: below --
2004-07-17 21:06 andre maute
2004-12-10 22:11 ` [Bug rtl-optimization/16613] [3.4 Regression] " andre maute
2004-12-10 23:10 ` Daniel Berlin
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=20041211032837.28282.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).