public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe.Miller@reuters.com
To: gcc-help@gcc.gnu.org
Subject: GCC Version?
Date: Mon, 06 May 2002 15:58:00 -0000	[thread overview]
Message-ID: <20020506155800.Pa_CC_JH7PqL4wgH_lCxdS9D0-mjQMDfJZXIsgSqBGc@z> (raw)

GCC Help,

My group is currently in the planning stages to port our Solaris codebase to the RedHat Linux 7.2 operating system.  It has been suggested to us to use GCC 2.96, but all information that we have read from the GCC website indicates that 2.96 is not a "formal" version.  We have been therefore considering using GCC 3.0.x, however we must link with third party static libraries built with GCC 2.95.3.  Are libraries built with GCC 2.95.3 binary compatible with GCC 3.0.x (i.e. can we link with 2.95.3 static libraries from 3.0.x)?  And since our primary goals for porting to Linux is performance oriented, are there any significant binary run-time performance advantages that GCC 3.0.x might provide over GCC 2.95.3?

Thank you for your time.

Joe Miller
Programmer Analyst
Reuters - Oak Brook, IL
joe.miller@reuters.com



-----------------------------------------------------------------
        Visit our Internet site at http://www.reuters.com

Any views expressed in this message are those of  the  individual
sender,  except  where  the sender specifically states them to be
the views of Reuters Ltd.

             reply	other threads:[~2002-05-06 22:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-06 15:58 Joe.Miller [this message]
     [not found] <20020506225929.615BB73D0F@violet.setuza.cz>
2002-05-06 22:25 ` Frank Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2002-05-06 15:58 Joe.Miller

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=20020506155800.Pa_CC_JH7PqL4wgH_lCxdS9D0-mjQMDfJZXIsgSqBGc@z \
    --to=joe.miller@reuters.com \
    --cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).