From: Joe Buck <Joe.Buck@synopsys.com>
To: bkoz@nabi.net
Cc: mark@codesourcery.com, gcc@gcc.gnu.org
Subject: Re: GCC 3.2 Prerelease
Date: Mon, 05 Aug 2002 15:45:00 -0000 [thread overview]
Message-ID: <200208052244.PAA26244@atrus.synopsys.com> (raw)
In-Reply-To: <20020805114603.0ba8cfce.bkoz@nabi.net> from "B. Kosnik" at Aug 05, 2002 11:46:03 AM
> Yes. Regardless of the Intel C++ ABI testsuite, I think my original
> point needs to be addressed: mainly, that 3.2 and 3.3 are at different
> C++ ABI's. I think this needs to be fixed.
Agreed; I don't see how we can release 3.2 unless we can be confident that
3.3, when released, will have the same ABI ("fixing" 3.3 before its
release, to fix the problem, might be acceptable). However, I must admit that I
am fuzzy about just what the breakage is; what are the differences?
next prev parent reply other threads:[~2002-08-05 22:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 11:46 B. Kosnik
2002-08-05 15:45 ` Joe Buck [this message]
2002-08-05 18:07 ` B. Kosnik
2002-08-05 19:02 ` H. J. Lu
2002-08-06 5:54 ` Daniel Jacobowitz
2002-08-06 8:07 ` Daniel Jacobowitz
2002-08-06 10:07 ` B. Kosnik
2002-08-06 8:47 ` Mark Mitchell
2002-08-06 10:04 ` B. Kosnik
2002-08-06 10:10 ` Phil Edwards
2002-08-07 7:43 ` Phil Edwards
2002-08-06 11:05 ` H. J. Lu
2002-08-06 11:21 ` Mark Mitchell
2002-08-06 11:30 ` H. J. Lu
2002-08-06 11:53 ` Neil Booth
2002-08-06 11:42 ` Joe Buck
2002-08-06 11:56 ` H. J. Lu
2002-08-06 11:46 ` Graham Stott
2002-08-06 11:37 ` Joe Buck
2002-08-06 11:59 ` H. J. Lu
2002-08-06 12:15 ` H. J. Lu
2002-08-06 12:17 ` H. J. Lu
2002-08-06 12:25 ` David Edelsohn
2002-08-06 14:14 ` Joe Buck
2002-08-06 20:29 ` Mark Mitchell
2002-08-06 22:17 ` B. Kosnik
2002-08-06 12:24 ` H. J. Lu
2002-08-06 12:37 ` H. J. Lu
-- strict thread matches above, loose matches on Subject: below --
2002-08-09 11:48 Mark Mitchell
2002-08-04 20:10 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=200208052244.PAA26244@atrus.synopsys.com \
--to=joe.buck@synopsys.com \
--cc=bkoz@nabi.net \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
/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).