This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: [g++] find build_headers, toplevel

To: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>
Subject: Re: [g++] find build_headers, toplevel
From: Alexandre Oliva <aoliva at redhat dot com>
Date: 22 Dec 2000 07:17:15 -0200
Cc: Benjamin Kosnik <bkoz at redhat dot com>, gcc-patches at gcc dot gnu dot org
Organization: GCC Team, Red Hat
References: <Benjamin Kosnik's message of "Mon, 18 Dec 2000 00:28:52 -0800(PST)"> <Pine.SOL.3.91.1001218002543.23773F-100000@cse.cygnus.com><4.3.2.7.2.20001218112656.00e472e0@mail.lauterbach.com>

On Dec 18, 2000, Franz Sirl <Franz.Sirl-kernel@lauterbach.com> wrote:

>> Besides, as soon as the v3 ABI stabilizes, we'll hopefully not have
>> another C++ ABI change in the next few years, and we're already
>> bumping the API number anyway, so it would be kind of pointless to
>> worry about it at this time.

> Well, I would be happier if we would worry _now_, instead of trying
> to cleanup later.

It makes no difference.  The only thing we have to guarantee is that,
whenever a binary incompatibility arises, the SONAME of the library
will change.  So, we can keep the SONAME simple for now and, if the
need for an additional SONAME tag ever arises, we can easily add it
back.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

References:
- Re: [g++] find build_headers, toplevel
  - From: Benjamin Kosnik
- Re: [g++] find build_headers, toplevel
  - From: Franz Sirl

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]