From: law@redhat.com
To: Mark Mitchell <mark@codesourcery.com>
Cc: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>,
Joe Buck <jbuck@synopsys.com>,
gcc@gcc.gnu.org
Subject: Re: Switching the default for -fabi-version
Date: Wed, 22 Oct 2003 15:18:00 -0000 [thread overview]
Message-ID: <200310221449.h9MEnqZZ024503@speedy.slc.redhat.com> (raw)
In-Reply-To: Your message of "22 Oct 2003 01:28:58 PDT." <1066811338.4002.6.camel@minax.codesourcery.com>
In message <1066811338.4002.6.camel@minax.codesourcery.com>, Mark Mitchell writ
es:
>
>> which are not very clear (may vs. will) and omitting of a reason (in case
>> of the second warning). So to say, if I can still specify -fabi-version=0
>> I'm happy with changing. But you could try to make sure you dont break
>> libstdc++ compatibility with this change?
>
>This is the point everyone seems to be missing: libstdc++ compatibility
>is *already* going to break in GCC 3.4.
But as you know, not everyone uses libstdc++ ;-)
>And, what, really is the benefit of keeping the default compiler ABI
>consistent with a previous version if the runtime library is going to
>bump its major version number?
The ability to build plug-ins for popular packages such as Mozilla.
The ability to interoperate with existing C++ runtimes that may not be
libstdc++.
>The only situation where the change I'm proposing would matter is when
>you're using the new compiler with the old library. That probably won't
>work anyhow -- since, for example, the new parser probably can't handle
>the old headers.
I wasn't aware of this.
>But, if, somehow, it would work without the change, it will also work
>with the change -- provided you add -fabi-version=1 to your command
>line.
That may ultimately be the answer. Bump up and allow folks who need it
to explicitly ask for the old ABI.
jeff
next prev parent reply other threads:[~2003-10-22 14:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 10:41 Richard Guenther
2003-10-22 10:55 ` Mark Mitchell
2003-10-22 11:32 ` Richard Guenther
2003-10-22 13:02 ` Allan Sandfeld
2003-10-22 13:57 ` Gabriel Dos Reis
2003-10-22 15:18 ` law [this message]
2003-10-22 15:23 ` Gabriel Dos Reis
2003-10-22 16:43 ` Mark Mitchell
2003-10-26 17:55 ` Florian Weimer
2003-10-26 19:10 ` Andreas Jaeger
2003-10-26 22:53 ` Florian Weimer
2003-10-27 0:46 ` Zack Weinberg
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 17:17 Benjamin Kosnik
2003-10-22 16:57 Benjamin Kosnik
2003-10-22 17:03 ` Mark Mitchell
2003-10-22 0:49 Mark Mitchell
2003-10-22 0:53 ` Joe Buck
2003-10-22 1:58 ` Mark Mitchell
2003-10-22 14:53 ` Michael Matz
2003-10-22 15:02 ` Allan Sandfeld
2003-10-22 15:02 ` Michael Matz
2003-10-22 15:09 ` law
2003-10-22 15:20 ` Michael Matz
2003-10-22 16:33 ` Mark Mitchell
2003-10-22 2:02 ` Mike Stump
2003-10-22 2:36 ` Mark Mitchell
2003-10-22 7:08 ` law
2003-10-22 8:28 ` Mark Mitchell
2003-10-22 8:30 ` law
2003-10-22 7:49 ` Joe Buck
2003-10-22 8:09 ` Mark Mitchell
2003-10-22 10:51 ` Nathan Sidwell
2003-10-22 11:03 ` Mark Mitchell
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=200310221449.h9MEnqZZ024503@speedy.slc.redhat.com \
--to=law@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.com \
--cc=mark@codesourcery.com \
--cc=rguenth@tat.physik.uni-tuebingen.de \
/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).