public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: gcc@gcc.gnu.org
Cc: "Goodman, Joe" <joe.goodman@intel.com>
Subject: Results from Intel´s C++ ABI Testsuite
Date: Sat, 06 Jul 2002 11:51:00 -0000	[thread overview]
Message-ID: <u81yagsp9g.fsf@gromit.moeb> (raw)


I've downloaded Intel's C++ ABI Testsuite (available via
http://developer.intel.com/software/products/opensource/) and run it
with both GCC 3.1 CVS and GCC 3.2 CVS to check for ABI problems on
i686-linux-gnu.

I get with both GCC 3.1 and 3.2 the following error:

/opt/gcc/3.1-devel/bin/g++ -g -DSTDIO_OK -DUSE_FUNCTION_DESCRIPTORS -c -o operator1.o operator1.cpp
missing=0; \
for name in `./extract_mangled_names.sh "operator1.cpp"`; do \
  if ! nm operator1.o | grep ${name}'$' > /dev/null; then \
    echo '  missing:' "${name}" >&2; \
    missing=1; \
  fi; \
done; \
if [ ${missing} = 1 ]; then \
  exit 1; \
fi
  missing: _Znwm
  missing: _Znam
make[1]: *** [operator1.pass] Error 1


This means that these two names are mangled wrongly:
// ::operator new (size_t)
//% mangled name: _Znwm

// ::operator new[] (size_t)
//% mangled name: _Znam

nm has instead:
         U _Znaj
         U _Znwj

The difference here is unsigned int versus unsigned long as type of
the operator.  I don't know whether this is a real bug or a problem in
the testsuite but it doesn't look critical to me.

The good news is that this is the only problem that the ABI Testsuite
showed with GCC, all other tests passed!

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

             reply	other threads:[~2002-07-06 18:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-06 11:51 Andreas Jaeger [this message]
2002-07-06 13:10 ` Results from Intel´s " Graham Stott
2002-07-06 13:28 ` Results from Intel4s " Nathan Sidwell
2002-07-10 13:40   ` Richard Henderson
2002-07-10 14:33     ` Joe Buck
2002-07-10 15:12       ` Gabriel Dos Reis
2002-07-10 21:14       ` Mark Mitchell
2002-07-11  9:56         ` Magnus Fromreide
2002-07-11 13:43           ` Richard Henderson
2002-07-20 20:50         ` Nick Ing-Simmons
2002-07-20 15:20           ` Richard Henderson
2002-07-22 13:41             ` Joe Buck

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=u81yagsp9g.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=joe.goodman@intel.com \
    /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).