From: "Matthew J. Turk" <m-turk@nwu.edu>
To: Doug Goldstein <cardoe@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GCC 3.1/3.2
Date: Sun, 28 Jul 2002 12:44:20 -0500 [thread overview]
Message-ID: <20020728174420.GA11994@dhcp101047.res-hall.nwu.edu> (raw)
In-Reply-To: <3D43F0B5.9030203@gentoo.org>
> 3.2 is labeled by GNU to be 100% multi-vender compliant with the C++ ABI
> now. Which is the core prob with the new gcc releases. By skipping
> straight to 3.2 we'll avoid 2 problem transitions.. 1 from 2.95 to 3.1
> and then from 3.1/3.1.1 to 3.2 instead we'll have 2.95 to 3.2.
The GCC Page (http://gcc.gnu.org/gcc-3.2/changes.html) says it is MultiVendor V3
compatible - does that mean that it's compatible (again) with 2.95? There
aren't any other changes listed on the page, so does that also mean that no
changes in code are required from 3.1 to 3.2 to compile? Will this just mean
going from 2.95 to 3.2 will be a matter of fixing the ISO C/C++ standards, just
as for going from 2.95 to 3.0?
mjt
---------------------------------------------------
Matthew J. Turk <m-turk@nwu.edu> ICQ: 3856787
"Music is the Best." - FZ thecatfishman.org
http://pubweb.nwu.edu/~mjt631/spamoff.htm
next prev parent reply other threads:[~2002-07-28 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 5:07 [gentoo-dev] GCC 3.1/3.2 Matthew J. Turk
2002-07-28 10:44 ` Bart Verwilst
2002-07-28 13:25 ` Doug Goldstein
2002-07-28 17:26 ` Terje Kvernes
2002-07-28 17:44 ` Matthew J. Turk [this message]
2002-07-28 18:27 ` Michael Mattsson
2002-07-28 22:16 ` Doug Goldstein
-- strict thread matches above, loose matches on Subject: below --
2002-07-28 22:01 Thomas Beaudry
2002-07-29 7:14 Michael Mattsson
2002-07-29 10:09 ` Matthew Kennedy
2002-07-29 7:28 Thomas Beaudry
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=20020728174420.GA11994@dhcp101047.res-hall.nwu.edu \
--to=m-turk@nwu.edu \
--cc=cardoe@gentoo.org \
--cc=gentoo-dev@gentoo.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