public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@cygnus.com>
To: martin@mira.isdn.cs.tu-berlin.de (Martin v. Loewis)
Cc: pfeifer@dbai.tuwien.ac.at, egcs@egcs.cygnus.com
Subject: Re: egcs 1.2 C++ ABI (Re: C++: STL 3.2)
Date: Mon, 26 Apr 1999 23:06:00 -0000	[thread overview]
Message-ID: <u9n1zu1ttp.fsf@yorick.cygnus.com> (raw)
In-Reply-To: <199904232313.BAA00817.cygnus.egcs@mira.isdn.cs.tu-berlin.de>

>>>>> Martin v Loewis <martin@mira.isdn.cs.tu-berlin.de> writes:

 > So far, I have identified two areas:
 > - STL is incompatible. The allocators all changed, resulting in a different
 >   default argument to any reasonable standard template, thus breaking
 >   all mangled names.

This is OK; so long as the data structures are similar enough the only harm
would be having two copies of the code in the executable.

 > - Some changes to exception handling. g++ now emits __start_cp_handler,
 >   which is not supported in egcs 1.1 libgcc. So, linking 1.2 compiled
 >   objects with 1.1 doesn't work.

But it is backward compatible.  I don't mind requiring people to use the
newest compiler to link mixed code.

 > a) Leave everything as-is, claiming no compatibility.

This is the way it has always been.  I think this is fine until the new ABI
is actually deployed, which should wait until it's finished -- and I'm
planning to do that this summer.

Jason

WARNING: multiple messages have this Message-ID
From: Jason Merrill <jason@cygnus.com>
To: martin@mira.isdn.cs.tu-berlin.de (Martin v. Loewis)
Cc: pfeifer@dbai.tuwien.ac.at, egcs@egcs.cygnus.com
Subject: Re: egcs 1.2 C++ ABI (Re: C++: STL 3.2)
Date: Fri, 30 Apr 1999 23:15:00 -0000	[thread overview]
Message-ID: <u9n1zu1ttp.fsf@yorick.cygnus.com> (raw)
Message-ID: <19990430231500.9K7FampAIBKDRJWURCkKgBWLEqSayenVWQR7Dam7I0w@z> (raw)
In-Reply-To: <199904232313.BAA00817.cygnus.egcs@mira.isdn.cs.tu-berlin.de>

>>>>> Martin v Loewis <martin@mira.isdn.cs.tu-berlin.de> writes:

 > So far, I have identified two areas:
 > - STL is incompatible. The allocators all changed, resulting in a different
 >   default argument to any reasonable standard template, thus breaking
 >   all mangled names.

This is OK; so long as the data structures are similar enough the only harm
would be having two copies of the code in the executable.

 > - Some changes to exception handling. g++ now emits __start_cp_handler,
 >   which is not supported in egcs 1.1 libgcc. So, linking 1.2 compiled
 >   objects with 1.1 doesn't work.

But it is backward compatible.  I don't mind requiring people to use the
newest compiler to link mixed code.

 > a) Leave everything as-is, claiming no compatibility.

This is the way it has always been.  I think this is fine until the new ABI
is actually deployed, which should wait until it's finished -- and I'm
planning to do that this summer.

Jason

  parent reply	other threads:[~1999-04-26 23:06 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-23  7:44 C++: STL 3.2 Gerald Pfeifer
1999-04-23 16:17 ` egcs 1.2 C++ ABI (Re: C++: STL 3.2) Martin v. Loewis
1999-04-24 15:52   ` Chip Salzenberg
1999-04-24 17:26     ` Martin v. Loewis
1999-04-24 18:11       ` Chip Salzenberg
1999-04-30 23:15         ` Chip Salzenberg
1999-04-30 23:15       ` Martin v. Loewis
1999-04-30 23:15     ` Chip Salzenberg
1999-04-24 23:14   ` Mark Mitchell
1999-04-25  5:16     ` Gerald Pfeifer
1999-04-30 23:15       ` Gerald Pfeifer
1999-04-30 23:15     ` Mark Mitchell
1999-04-30 23:15   ` Martin v. Loewis
1999-04-24 22:28 ` C++: STL 3.2 Jeffrey A Law
1999-04-24 23:11   ` Mark Mitchell
1999-04-25 13:04     ` Martin v. Loewis
1999-04-30 23:15       ` Martin v. Loewis
1999-04-30 23:15     ` Mark Mitchell
1999-04-25 12:50   ` Martin v. Loewis
1999-04-25 14:46     ` Gabriel Dos_Reis
1999-04-30 23:15       ` Gabriel Dos_Reis
1999-04-30 23:15     ` Martin v. Loewis
1999-04-30 23:15   ` Jeffrey A Law
     [not found] ` <199904232313.BAA00817.cygnus.egcs@mira.isdn.cs.tu-berlin.de>
1999-04-26 23:06   ` Jason Merrill [this message]
1999-04-27  0:06     ` egcs 1.2 C++ ABI (Re: C++: STL 3.2) Martin v. Loewis
1999-04-27  0:18       ` Jason Merrill
1999-04-30 23:15         ` Jason Merrill
1999-04-30 23:15       ` Martin v. Loewis
1999-04-30 23:15     ` Jason Merrill
1999-04-30 23:15 ` C++: STL 3.2 Gerald Pfeifer
1999-04-27 14:37 egcs 1.2 C++ ABI (Re: C++: STL 3.2) Ross Smith
1999-04-27 15:25 ` Martin v. Loewis
1999-04-30 23:15   ` Martin v. Loewis
1999-04-30 23:15 ` Ross Smith

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=u9n1zu1ttp.fsf@yorick.cygnus.com \
    --to=jason@cygnus.com \
    --cc=egcs@egcs.cygnus.com \
    --cc=martin@mira.isdn.cs.tu-berlin.de \
    --cc=pfeifer@dbai.tuwien.ac.at \
    /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).