public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: Andreas Jaeger <aj@suse.de>
Cc: gcc@gcc.gnu.org, "Goodman, Joe" <joe.goodman@intel.com>
Subject: Re: Results from Intel4s C++ ABI Testsuite
Date: Sat, 06 Jul 2002 13:28:00 -0000	[thread overview]
Message-ID: <3D2740E8.D9D3A105@codesourcery.com> (raw)
In-Reply-To: <u81yagsp9g.fsf@gromit.moeb>

Andreas Jaeger wrote:

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

>   missing: _Znwm
>   missing: _Znam
> make[1]: *** [operator1.pass] Error 1

> 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.
yes. I agree. this is operator new (size_t), the ABI does not
specify what type size_t should be, and 18.1/1 says size_t comes
from cstddef, which has the same contents as C header stddef.h, modulo
some changes. I don't have a C std in front of me, but IIRC size_t
is the first of 'unsigned int', 'unsigned long', 'unsigned long long'
that can hold an object's size. So, on an ILP32 machine, it will be
'unsigned int' and operator new (size_t) will be _Znwj. If
size_t is implementation defined, then we need to fix the ABI document
to specify the choice.

nathan

-- 
Dr Nathan Sidwell   ::   http://www.codesourcery.com   ::   CodeSourcery LLC
         'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org

  parent reply	other threads:[~2002-07-06 19:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-06 11:51 Results from Intel´s " Andreas Jaeger
2002-07-06 13:10 ` Graham Stott
2002-07-06 13:28 ` Nathan Sidwell [this message]
2002-07-10 13:40   ` Results from Intel4s " 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=3D2740E8.D9D3A105@codesourcery.com \
    --to=nathan@codesourcery.com \
    --cc=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).