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]
Other format: [Raw text]

Re: ABI Issues: C++ PATCH: PR 12053


mark@codesourcery.com (Mark Mitchell)  wrote on 03.09.03 in <1062632993.31887.15.camel@doubledemon.codesourcery.com>:

> On Wed, 2003-09-03 at 16:34, Joe Buck wrote:
> > On Wed, Sep 03, 2003 at 04:16:43PM -0700, Mark Mitchell wrote:
> > > > In any case, we should make sure that -Wabi issues a warning for this
> > > > case.  The goal for -Wabi should be that if we run it using the latest
> > > > available GCC and it is silent, we have ABI compatibility with
> > > > everything from 3.2 on (barring issues with libraries).
        **********************
> > >
> > > There's no place to put such a warning -- 3.3.2 *will* be compatible
> > > with 3.2 (now that this fix is in), so it can't warn.  And 3.3.1 is
> > > already in the can, so it can't warn either.
> >
> > Sure there is: 3.3.2 can warn about the problem in 3.3.1.  To know about
> > problems, people will have to run the check with the newest available
> > compiler.
>
> That's different from what you said above, I think.
>
> You said silence->3.2-compat.

No, he said silence->3.2...current compat, a very different thing.

> That doesn't of course, imply that
> noise->3.2-incompat, but that seems logical.  Now, you're suggesting
> that noise->incompat-3.2-or-3.3-or-3.3.1.

Which is exactly what he proposed before.

MfG Kai


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