public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de>
To: <libstdc++@gcc.gnu.org>
Cc: <gcc@gcc.gnu.org>
Subject: Results for g++ 3.1 application testing on i686-pc-linux-gnu
Date: Sun, 03 Mar 2002 18:44:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.30.0203040443120.1388-100000@snake.iap.physik.tu-darmstadt.de> (raw)

I tested g++ 3.1 20020302 versus some applications:

Here are the results:

current boost cvs:
All tests pass. g++ does not provide the zero sized base class
optimization. Therefore, there are seven "failures" for empty_* types in
object_type_traits_test.cpp.

blitz-20001213:
Compiling wei-ku-1.cpp crashes the compiler when
optimization is on. Cf. PR c++/5504 (gcc 3.0 regression).

root_v3.02.07:
Everything works, except for test/bench.cxx, as for gcc 3.0.

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

Code from Josuttis' Book "The C++ Standard Library":

Everything works fine, except for the parsing of doubles on input when
the locale is set to de_DE (PR libstdc++/5816, grouping related) and
the unresolved state of PR libstc++/5133.

stepanov_v1p2.C:

-O
Abstraction Penalty: 1.14
-O2
Abstraction Penalty: 1.30
-O3
Abstraction Penalty: 1.30
-O2  -finline-limit=10000
Abstraction Penalty: 1.30
-O2  -finline-limit=100000
Abstraction Penalty: 1.30

mtl-2.1.2-20:
No problems detected, after applying patches for missing typename
warnings.

STLport-4.5.3
No problems detected. All tests pass.

System setup:
SuSE 7.3
Glibc 2.2.4 + patches
Linux 2.4.17
binutils version 2.11.93.0.2
g++ -v
Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs
Configured with: ../gcc/configure --enable-shared --disable-nls --enable-threads --enable-languages=c,c++,f77,objc
Thread model: posix
gcc version 3.1 20020302 (prerelease)

Hope this helps,

Peter Schmid

             reply	other threads:[~2002-03-04  2:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-03 18:44 Peter Schmid [this message]
2002-03-03 20:45 ` Craig Rodrigues
2002-03-03 23:55   ` Benjamin Kosnik
2002-03-04  5:54     ` Stephen M.Webb
2002-03-04  9:13       ` Benjamin Kosnik
2002-03-05 11:47       ` Stephen M. Webb
     [not found]       ` <200203051947.UAA06990@mayo.cmla.ens-cachan.fr>
2002-03-05 12:31         ` Gabriel Dos Reis
2002-03-05 13:11           ` Benjamin Kosnik
2002-03-05 14:04             ` Gabriel Dos Reis
2002-03-05 14:09               ` Benjamin Kosnik
2002-03-05 15:03             ` Richard Henderson
2002-03-05 17:25               ` Benjamin Kosnik
2002-03-05 23:00               ` Gabriel Dos Reis
2002-03-06 13:26                 ` Richard Henderson
2002-03-06  1:21               ` Gabriel Dos Reis
2002-03-06 13:30                 ` Richard Henderson
2002-03-05 15:02           ` Richard Henderson
2002-03-05 22:56             ` Gabriel Dos Reis
2002-03-07 10:47     ` Peter Schmid
2002-03-07 23:24       ` Benjamin Kosnik
2002-03-04 18:25 ` Benjamin Kosnik
2002-03-04 21:10   ` Craig Rodrigues
2002-04-20 16:17 Peter Schmid
2002-05-05 17:29 Peter Schmid

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.30.0203040443120.1388-100000@snake.iap.physik.tu-darmstadt.de \
    --to=schmid@snake.iap.physik.tu-darmstadt.de \
    --cc=gcc@gcc.gnu.org \
    --cc=libstdc++@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).