From: Andrew Haley <aph-gcc@littlepinkcloud.COM>
To: "Ахметов Казбек" <k_akhmetov@af.kz>
Cc: gcc-help@gcc.gnu.org
Subject: Re: i686-gcc vs i586-Suse Linux
Date: Wed, 06 Jun 2007 08:56:00 -0000 [thread overview]
Message-ID: <18022.30395.259859.150576@zebedee.pink> (raw)
In-Reply-To: <739430768.20070606144227@af.kz>
??????? ?????? writes:
> ?ould you give me a confirmation that:
> 'The installation of the 'i686' gcc is compatable with the 'i586'
> version of Suse Linux' ?
I don't really understand why you're asking this. If you have a i586
system, why not configure gcc for the i586 ?
The most significant difference between i586 (Pentium) and i686
(Pentium Pro) from gcc's point of view is MMX instructions.
Andrew.
next prev parent reply other threads:[~2007-06-06 8:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 8:49 Ахметов Казбек
2007-06-06 8:56 ` Andrew Haley [this message]
2007-06-06 13:25 ` Martin Krischik
2007-06-10 20:12 ` Martin Krischik
2007-06-10 20:55 ` Andrew Haley
2007-06-06 14:23 ` Atwood, Robert C
2007-06-06 16:26 ` Andrew Haley
2007-06-06 20:31 ` Atwood, Robert C
2007-06-07 10:31 ` Martin Krischik
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=18022.30395.259859.150576@zebedee.pink \
--to=aph-gcc@littlepinkcloud.com \
--cc=gcc-help@gcc.gnu.org \
--cc=k_akhmetov@af.kz \
/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).