public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* GCC version compatible problem
@ 2004-03-12 19:26 Lu Peng
  2004-03-12 19:41 ` Kazu Hirata
  0 siblings, 1 reply; 6+ messages in thread
From: Lu Peng @ 2004-03-12 19:26 UTC (permalink / raw)
  To: gcc


Dear gcc team,

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?

thanks a lot,

Lu Peng


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: GCC version compatible problem
  2004-03-12 19:26 GCC version compatible problem Lu Peng
@ 2004-03-12 19:41 ` Kazu Hirata
  2004-03-12 19:47   ` Lu Peng
  0 siblings, 1 reply; 6+ messages in thread
From: Kazu Hirata @ 2004-03-12 19:41 UTC (permalink / raw)
  To: lpeng; +Cc: gcc

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: GCC version compatible problem
  2004-03-12 19:41 ` Kazu Hirata
@ 2004-03-12 19:47   ` Lu Peng
  2004-03-12 20:09     ` Eric Christopher
  0 siblings, 1 reply; 6+ messages in thread
From: Lu Peng @ 2004-03-12 19:47 UTC (permalink / raw)
  To: Kazu Hirata; +Cc: gcc

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: GCC version compatible problem
  2004-03-12 19:47   ` Lu Peng
@ 2004-03-12 20:09     ` Eric Christopher
  2004-03-12 20:18       ` Joseph S. Myers
  0 siblings, 1 reply; 6+ messages in thread
From: Eric Christopher @ 2004-03-12 20:09 UTC (permalink / raw)
  To: Lu Peng; +Cc: Kazu Hirata, gcc

On Fri, 2004-03-12 at 11:47, Lu Peng wrote:
> 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.

No, gcc specific extensions should still work, though bug fixes or
deprecated features are still bug fixes and deprecated features.

An example would perhaps be more help in this case.

-eric

-- 
Eric Christopher <echristo@redhat.com>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: GCC version compatible problem
  2004-03-12 20:09     ` Eric Christopher
@ 2004-03-12 20:18       ` Joseph S. Myers
  2004-03-12 21:49         ` Eric Christopher
  0 siblings, 1 reply; 6+ messages in thread
From: Joseph S. Myers @ 2004-03-12 20:18 UTC (permalink / raw)
  To: Eric Christopher; +Cc: Lu Peng, Kazu Hirata, gcc

On Fri, 12 Mar 2004, Eric Christopher wrote:

> No, gcc specific extensions should still work, though bug fixes or
> deprecated features are still bug fixes and deprecated features.

But deprecation follows a single-release cycle: a feature is OK in release
n, deprecated (accepted with a warning) in n+1 and rejected in n+2 (where
3.1 and 3.2 count as the same release for this purpose).  Thus features
present in 2.95 may well be gone in 3.2; for various reasons users and
distributors don't necessarily use each successive release, but for
deprecations in FSF GCC the release cycle of FSF GCC is what's relevant.

We no longer follow an "embrace and extend" principle of encouraging use
of extensions; extensions that do not add expressive power to the
languages are liable to be deprecated and then removed if they impose
significant costs in the maintainability of the code supporting standard
language features.

-- 
Joseph S. Myers
jsm@polyomino.org.uk

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: GCC version compatible problem
  2004-03-12 20:18       ` Joseph S. Myers
@ 2004-03-12 21:49         ` Eric Christopher
  0 siblings, 0 replies; 6+ messages in thread
From: Eric Christopher @ 2004-03-12 21:49 UTC (permalink / raw)
  To: Joseph S. Myers; +Cc: Lu Peng, Kazu Hirata, gcc

On Fri, 2004-03-12 at 12:18, Joseph S. Myers wrote:
> On Fri, 12 Mar 2004, Eric Christopher wrote:
> 
> > No, gcc specific extensions should still work, though bug fixes or
> > deprecated features are still bug fixes and deprecated features.
> 
> But deprecation follows a single-release cycle: a feature is OK in release

Thanks for being more clear than I apparently was.

-eric

-- 
Eric Christopher <echristo@redhat.com>

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2004-03-12 21:49 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-12 19:26 GCC version compatible problem Lu Peng
2004-03-12 19:41 ` Kazu Hirata
2004-03-12 19:47   ` Lu Peng
2004-03-12 20:09     ` Eric Christopher
2004-03-12 20:18       ` Joseph S. Myers
2004-03-12 21:49         ` Eric Christopher

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).