public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de>
To: gcc@gcc.gnu.org
Subject: Results for g++ 3.0.3 application testing on i686-pc-linux-gnu
Date: Sat, 15 Dec 2001 16:34:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0112160107120.3036-100000@snake.iap.physik.tu-darmstadt.de> (raw)

I tested g++ 3.0.3 20011215 (prerelease) versus some applications.
Here are the results:

current boost cvs:
All tests pass.
Cv-qualified references are not implemented, PR C++/2645.

blitz-20001213:
No problems detected after increasing -ftemplate-depth to 100. 
All tests pass.

root_v3.02.05:
Everything works, except for test/bench.cxx.

pooma-gcc:
No problems detected. All tests pass.

Code from Josuttis' Book "The C++ Standard Library":
Everything works except for the problems reported in PRs
libstdc++/3679 and libstdc++/3720, partly fixed; both of them are fixed
on the main line.   

stepanov_v1p2.C:
-O2				Abstraction Penalty: 1.19
-O3				Abstraction Penalty: 3.82
-O2  -finline-limit=10000	Abstraction Penalty: 1.22
-O2  -finline-limit=100000	Abstraction Penalty: 1.20

mtl-2.1.2-19:
No problems detected.

STLport-4.5
No problems detected. All tests pass.

System setup:
SuSE 7.3
Glibc 2.2.4
Linux 2.4.14
binutils version 2.11.90.0.29
Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.0.3/specs
Configured with: ../gcc-3.0/configure --enable-shared --disable-nls --enable-threads=posix --enable-clocale=gnu --enable-languages=c,c++,f77,objc
Thread model: posix
gcc version 3.0.3 20011215 (prerelease)

Hope this helps,

Peter Schmid

             reply	other threads:[~2001-12-16  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-15 16:34 Peter Schmid [this message]
2001-12-17  9:42 ` Mark Mitchell
2001-12-15 19:11 Benjamin Kosnik

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=Pine.LNX.4.21.0112160107120.3036-100000@snake.iap.physik.tu-darmstadt.de \
    --to=schmid@snake.iap.physik.tu-darmstadt.de \
    --cc=gcc@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).