From: Neil Ferguson <nferguso@eso.org>
To: gcc-help@gcc.gnu.org
Subject: Minimum GCC version to safely compile 64-bit binaries for AMD64?
Date: Wed, 31 Aug 2005 17:52:00 -0000 [thread overview]
Message-ID: <4315EE33.3090900@eso.org> (raw)
Hi -
We are considering buying some AMD64 machines, but are presently standardised
on GCC 3.3. We're one of those places that finds a version that works for us
and sticks with it, so an update is hard to sell. People are especially leery
of the latest stable release - we like our compilers to have been out there
for a while, on the basis that they're more likely to have been exposed to
everything the users could throw at them.
Can GCC 3.3 compile 64-bit binaries that work reliably on AMD64?
What would the minimum recommended version of GCC be? (I'd be curious to know
even if GCC 3.3 is OK, for my own historical interest.)
I've tried searching gcc.gnu.org and with Google, but I'm having trouble
finding an authoritative answer. As one would expect, the current up-front
information on the GCC site focuses on 3.4 and 4.0.
Neil.
next reply other threads:[~2005-08-31 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 17:52 Neil Ferguson [this message]
2005-09-04 0:19 ` Bob Proulx
2005-09-06 14:10 ` Neil Ferguson
2005-09-06 15:23 ` Bob Proulx
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=4315EE33.3090900@eso.org \
--to=nferguso@eso.org \
--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).