public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lu Peng <lpeng@cise.ufl.edu>
To: Kazu Hirata <kazu@cs.umass.edu>
Cc: <gcc@gcc.gnu.org>
Subject: Re: GCC version compatible problem
Date: Fri, 12 Mar 2004 19:47:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0403121444250.18217-100000@sand.cise.ufl.edu> (raw)
In-Reply-To: <20040312.144117.64783556.kazu@cs.umass.edu>

Thanks for your reply. So if my programs have some gcc-specific
extensions, then they are hopeless in gcc 3.X? The problem is that
these programs are big and written by others. I can't do line-by-line
inspection of the programs. What I expect is that the new gcc version
can compile old programs.

thanks,

Lu



On Fri, 12 Mar 2004, Kazu Hirata wrote:

> Hi Lu,
>
> > I got some gcc version updating problem. I have some programs which
> > run well with gcc 2.96 (in RH 7.3) but always failed with gcc 3.2.2
> > (in RH 9.0). Does gcc have compatiblity to old versions? If so, could
> > you tell me what I should do?
>
> GCC 3.x has closer conformance to the language standard.  Also, some
> GCC-specific extensions are being removed, so your program may have
> tripped over these things.
>
> Not to mention, there is always a possibility of a bug in GCC
> itself. :-)
>
> Kazu Hirata
>
>

  reply	other threads:[~2004-03-12 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12 19:26 Lu Peng
2004-03-12 19:41 ` Kazu Hirata
2004-03-12 19:47   ` Lu Peng [this message]
2004-03-12 20:09     ` Eric Christopher
2004-03-12 20:18       ` Joseph S. Myers
2004-03-12 21:49         ` Eric Christopher

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=Pine.GSO.4.33.0403121444250.18217-100000@sand.cise.ufl.edu \
    --to=lpeng@cise.ufl.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=kazu@cs.umass.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).