public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: albaugh@agames.com (Mike Albaugh)
To: help-gcc@gnu.org
Subject: Re: Linking problems, mangling ?
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <83bcc9$s2p$1@null.agames.com> (raw)
Message-ID: <19991231222400.W3D35e1j62vtUnsR3gzGR6FzklmIfMx5EwpYYJF9XAA@z> (raw)
In-Reply-To: <83avtd$9bj$1@news.tue.nl>

Eric Meijer (tgakem@pebbles.chem.tue.nl) wrote:

: [...], and so on, so if the name mangling were made the same, your
: programs would link against libraries provided from other compilers
: but then crash when run. For this reason, the ARM encourages compiler
: writers to make their name mangling different from that of other
: compilers for the same platform. Incompatible libraries are then
: detected at link time, rather than at run time.

: ------------------------------------------------------------------------

: This means that you need to compile all C++ source in an application
: with one and the same compiler.  With C libraries this problem generally
: doesn't exist.

	Beg to differ. On _many_ platforms, the C libraries from
different vendors (and even from different switch settings to the
same compiler) can and do differ in such things as parameter types,
structure layouts, etc. Heck MSVC's "intrinsic" functions disagree
with their own .h files, sometimes :-) Anyway, the result of these
"bleeding ends" is not typically detected at link time, but either
at compile time (_if_ the programmer cranks warnings up high enough
_and_ the .h files are complete and correct) or at run-time, where
they manifest themselves as obscure behavior.

						Mike
| albaugh@agames.com, speaking only for myself

  parent reply	other threads:[~1999-12-31 22:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-16  6:36 Roland TTK
1999-12-16  7:23 ` Eric Meijer
1999-12-16  8:58   ` Roland TTK
1999-12-16 11:57     ` Dave Sieber
1999-12-31 22:24       ` Dave Sieber
1999-12-17 11:52     ` David C.
1999-12-31 22:24       ` David C.
1999-12-31 22:24     ` Roland TTK
1999-12-16 11:06   ` Mike Albaugh [this message]
1999-12-31 22:24     ` Mike Albaugh
1999-12-31 22:24   ` Eric Meijer
1999-12-31 22:24 ` Roland TTK

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='83bcc9$s2p$1@null.agames.com' \
    --to=albaugh@agames.com \
    --cc=help-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).