From: Mark Mitchell <mark@codesourcery.com>
To: Joe Buck <Joe.Buck@synopsys.com>, Richard Henderson <rth@redhat.com>
Cc: Nathan Sidwell <nathan@codesourcery.com>,
Andreas Jaeger <aj@suse.de>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
Goodman Joe <joe.goodman@intel.com>
Subject: Re: Results from Intel4s C++ ABI Testsuite
Date: Wed, 10 Jul 2002 21:14:00 -0000 [thread overview]
Message-ID: <35210000.1026337826@warlock.codesourcery.com> (raw)
In-Reply-To: <200207102041.NAA27631@atrus.synopsys.com>
> It seems that for true C++ binary compatibility all implementers must
> agree on the type of size_t. Was this overlooked?
Sort of.
As Richard says, this is pretty much a property of the OS. If "int" and
"long" are the same, you can interchange the two for binary compatibility
purposes, but you'll never make your header files work right.
And, of course, since "size_t" is just a typedef we can't mangle it
specially, even if we wanted to.
It is true that if my OS uses "long" and yours uses "int" -- but they
are the same in all other ways -- then I can't mix and match C++ shared
objects from our two systems. I can still mix and match C++ shared
objects from any one of those systems, even if I used different
compilers to build them.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-07-10 21:52 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 ` 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 [this message]
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=35210000.1026337826@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=Joe.Buck@synopsys.com \
--cc=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=joe.goodman@intel.com \
--cc=nathan@codesourcery.com \
--cc=rth@redhat.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).