From: Gabriel Dos Reis <gdr@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Mark Mitchell <mark@codesourcery.com>,
"obrien@freebsd.org" <obrien@freebsd.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: C++ binary compatibility between GCC 3.1 and GCC 3.2?
Date: Sat, 06 Jul 2002 07:20:00 -0000 [thread overview]
Message-ID: <m3d6u16l7p.fsf@merlin.nerim.net> (raw)
In-Reply-To: Jakub Jelinek's message of "Sat, 6 Jul 2002 14:40:23 +0200"
Jakub Jelinek <jakub@redhat.com> writes:
| But if 3.1.2 was called 3.2, it would not be minor release but major, thus
| could introduce ABI incompatibilities.
As I understand people are objecting to having 3.1.x not binrary
compatible with 3.2.y.
| Apple could stay at 3.1, while Linux vendors, FreeBSD and whoever
| is currently preparing 3.1.x based distribution could still switch to this
| 3.2 and be (hopefully) binary compatible with the upcoming 3.3
| (current trunk).
-- Gaby
next prev parent reply other threads:[~2002-07-06 13:28 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 9:55 Andreas Jaeger
2002-07-04 10:23 ` H. J. Lu
2002-07-05 14:17 ` Mark Mitchell
2002-07-05 14:22 ` Andreas Jaeger
2002-07-05 14:28 ` Mark Mitchell
2002-07-05 14:53 ` David O'Brien
2002-07-05 15:08 ` Mark Mitchell
2002-07-06 5:34 ` Andreas Jaeger
2002-07-06 6:40 ` Gabriel Dos Reis
2002-07-06 6:40 ` Jakub Jelinek
2002-07-06 7:20 ` Gabriel Dos Reis [this message]
2002-07-06 7:53 ` Andreas Jaeger
2002-07-06 8:54 ` Gabriel Dos Reis
2002-07-06 11:04 ` Daniel Jacobowitz
2002-07-06 7:42 ` Andreas Jaeger
2002-07-06 11:08 ` Jeff Law
2002-07-06 11:10 ` Gwenole Beauchesne
2002-07-06 6:19 ` Daniel Egger
2002-07-05 14:46 ` David O'Brien
2002-07-05 15:02 ` Mark Mitchell
2002-07-06 6:28 ` Scott Robert Ladd
2002-07-05 15:02 ` H. J. Lu
2002-07-05 15:12 ` David O'Brien
2002-07-05 15:20 ` H. J. Lu
2002-07-05 16:11 ` Stan Shebs
2002-07-05 16:12 ` David Edelsohn
2002-07-05 16:35 ` Stan Shebs
2002-07-05 22:18 ` Geoff Keating
2002-07-07 23:14 ` Mark Mitchell
2002-07-06 4:56 ` Andreas Jaeger
2002-07-06 6:44 ` Gerald Pfeifer
2002-07-06 7:35 ` Andreas Jaeger
2002-07-06 11:44 ` David O'Brien
2002-07-05 22:35 ` David Edelsohn
2002-07-06 5:40 ` Joseph S. Myers
2002-07-06 6:40 ` Gabriel Dos Reis
2002-07-06 7:49 ` Andreas Jaeger
-- strict thread matches above, loose matches on Subject: below --
2002-07-10 4:24 Iain McClatchie
2002-07-08 10:09 Ben Woodhead
2002-07-08 9:02 Bernard Dautrevaux
2002-07-08 13:03 ` Bernard Dautrevaux
2002-07-10 7:32 ` Bernard Dautrevaux
2002-07-12 3:09 ` Bernard Dautrevaux
2002-07-12 13:50 ` Bernard Dautrevaux
2002-07-08 3:42 Bernard Dautrevaux
2002-07-08 4:07 ` Gabriel Dos Reis
2002-07-08 6:28 ` Joern Rennecke
2002-07-08 13:05 ` Bernard Dautrevaux
2002-07-10 7:33 ` Bernard Dautrevaux
2002-07-12 4:27 ` Bernard Dautrevaux
2002-07-12 13:53 ` Bernard Dautrevaux
2002-07-06 15:47 Joern Rennecke
2002-07-06 16:09 ` Gabriel Dos Reis
2002-07-07 8:03 ` Joern Rennecke
[not found] <3900A36C.18989ED4@apple.com>
2000-04-21 17:17 ` [patch] beginnings of the macro rewrite Horst von Brand
2000-04-22 10:33 ` Zack Weinberg
2000-04-22 20:13 ` Marc Espie
2000-04-22 20:20 ` Neil Booth
2000-04-24 8:57 ` Michael Meissner
2000-04-24 17:54 ` Russ Allbery
2000-04-27 15:54 ` Philipp Thomas
2000-04-27 17:32 ` Joe Buck
2000-04-24 23:38 ` Martin Kahlert
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=m3d6u16l7p.fsf@merlin.nerim.net \
--to=gdr@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mark@codesourcery.com \
--cc=obrien@freebsd.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).