From: Mike Stump <mrs@wrs.com>
To: martin@mira.isdn.cs.tu-berlin.de, pfeifer@dbai.tuwien.ac.at
Cc: gcc@gcc.gnu.org, landauer@apple.com
Subject: Re: ABI/compatibility details? (egcs -> gcc 2.95 -> future?)
Date: Sun, 31 Oct 1999 23:35:00 -0000 [thread overview]
Message-ID: <199910081838.LAA23380@kankakee.wrs.com> (raw)
Message-ID: <19991031233500.JQW8A6jOrQpn8iVMg8tjOk108QeYswklfg-U3YRCy2s@z> (raw)
> Date: Fri, 8 Oct 1999 19:28:20 +0200
> From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
> I think last time we discussed that, there was some kind of
> agreement *not* to document the ABI differences. Instead, the
> "official" party line is that there is no compatibility whatsoever
> between major compiler versions, and any reports to the contrary are
> pure luck. [ the context for this was c++ (I hope) ]
Since we have now proven that we can't maintain compatibility, I think
it would be wise to turn on -fnew-abi features that are near stable,
so that we can finish testing and stabilizing them for the next major
release. For example -fsquangle is an excellent example.
Jason, any plans to start turning this type of stuff on?
next reply other threads:[~1999-10-31 23:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-08 11:38 Mike Stump [this message]
1999-10-08 11:48 ` Gerald Pfeifer
1999-10-08 13:28 ` Mark Mitchell
1999-10-08 22:05 ` Gerald Pfeifer
1999-10-09 4:10 ` Martin v. Loewis
1999-10-31 23:35 ` Martin v. Loewis
1999-10-31 23:35 ` Gerald Pfeifer
1999-10-31 23:35 ` Mark Mitchell
1999-10-31 23:35 ` Gerald Pfeifer
1999-10-31 23:35 ` Mike Stump
-- strict thread matches above, loose matches on Subject: below --
1999-09-20 11:20 egcs and altivec vector type David Young
1999-09-20 14:10 ` ABI/compatibility details? (egcs -> gcc 2.95 -> future?) Doug Landauer
1999-09-20 14:17 ` Alex Buell
1999-09-20 15:04 ` Martin v. Loewis
1999-09-20 15:16 ` Alex Buell
1999-09-20 15:46 ` Martin v. Loewis
1999-09-20 17:34 ` Alexandre Oliva
1999-09-21 0:00 ` Alex Buell
1999-09-30 18:02 ` Alex Buell
1999-09-30 18:02 ` Alexandre Oliva
1999-09-21 1:26 ` Wolfram Gloger
1999-09-21 12:16 ` Alex Buell
1999-09-22 1:09 ` Wolfram Gloger
1999-09-22 15:29 ` Alex Buell
1999-09-30 18:02 ` Alex Buell
1999-09-30 18:02 ` Wolfram Gloger
1999-09-30 18:02 ` Alex Buell
1999-09-30 18:02 ` Wolfram Gloger
1999-09-30 18:02 ` Martin v. Loewis
1999-09-30 18:02 ` Alex Buell
1999-09-30 18:02 ` Martin v. Loewis
1999-09-30 18:02 ` Alex Buell
1999-09-20 15:23 ` Martin v. Loewis
1999-09-24 13:10 ` Gerald Pfeifer
1999-09-30 18:02 ` Gerald Pfeifer
1999-10-08 10:36 ` Martin v. Loewis
1999-10-31 23:35 ` Martin v. Loewis
1999-09-30 18:02 ` Martin v. Loewis
1999-09-30 18:02 ` Doug Landauer
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=199910081838.LAA23380@kankakee.wrs.com \
--to=mrs@wrs.com \
--cc=gcc@gcc.gnu.org \
--cc=landauer@apple.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).