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/4.0 Regression] compile time regression, when adding cerr usage
Date: Thu, 05 May 2005 20:12:00 -0000	[thread overview]
Message-ID: <20050505201240.24713.qmail@sourceware.org> (raw)
In-Reply-To: <20040718101108.16613.andre.maute@gmx.de>


------- Additional Comments From andre dot maute at gmx dot de  2005-05-05 20:12 -------
i want to supplement my compile time tests which shows that a regression  
was introduced between 2005/03/26 an 2005/04/02  
  
> g++-4.0-20050402 -v  
Using built-in specs.  
Target: i686-pc-linux-gnu  
Configured with: ../gcc-4.0-20050402/configure --prefix=/opt/gcc-4.0-20050402  
--program-suffix=-4.0-20050402 --enable-shared --enable-languages=c,c++  
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu  
--disable-nls --disable-checking --with-arch=pentium3  
Thread model: posix  
gcc version 4.0.0 20050402 (prerelease)  
  
> time g++-4.0-20050402 -c -O3 -D __NDEBUG__ compiletimetest2.cc  
real    0m52.126s    user    0m51.187s    sys     0m0.777s  
  
> time g++-4.0-20050402 -c -O3 -D __DEBUG__ compiletimetest2.cc  
real    0m55.409s    user    0m54.280s    sys     0m0.935s  
  
> g++-4.0-20050402 -c -O3 -D __NDEBUG__ compiletimetest2.cc -save-temps  
> ls -al compiletimetest2.s  
-rw-r--r--    1 login500  users     1186149 May  5 22:05 compiletimetest2.s  
  
Regards Andre  

-- 


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


  parent reply	other threads:[~2005-05-05 20:12 UTC|newest]

Thread overview: 21+ 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
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 [this message]
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
     [not found] <bug-16613-6020@http.gcc.gnu.org/bugzilla/>
2006-03-11  3:17 ` mmitchel 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=20050505201240.24713.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).