public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Beaudry" <tmbeaudry@msn.com>
To: m-turk@nwu.edu, cardoe@gentoo.org
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GCC 3.1/3.2
Date: Sun, 28 Jul 2002 22:01:00 +0000	[thread overview]
Message-ID: <F17k3reOtms2zrHp3Bn0002a324@hotmail.com> (raw)

>The GCC Page (http://gcc.gnu.org/gcc-3.2/changes.html) says it is
>MultiVendor V3 compatible

ABI = Application Binary Interface.  What vendors of debuggers and
other tools see when they work with the output of GCC.  3.2 is
compatible with version 3 of the spec.

>- 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?

Anything that compiled with 3.x will compile without change with
3.2.  As stated, the only changes are to the ABI, what other tools
interface with.

Thus you would need the same changes to 2.95 code as you would for any
of the other 3.x compilers.  My experience has been that bringing the
code into compliance with the ISO standards will fix any problems.


_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx



             reply	other threads:[~2002-07-28 22:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-28 22:01 Thomas Beaudry [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-29  7:28 [gentoo-dev] GCC 3.1/3.2 Thomas Beaudry
2002-07-29  7:14 Michael Mattsson
2002-07-29 10:09 ` Matthew Kennedy
2002-07-28  5:07 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
2002-07-28 18:27     ` Michael Mattsson
2002-07-28 22:16       ` Doug Goldstein

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=F17k3reOtms2zrHp3Bn0002a324@hotmail.com \
    --to=tmbeaudry@msn.com \
    --cc=cardoe@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=m-turk@nwu.edu \
    /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