From: Jim Wilson <wilson@cygnus.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Recommended compiler for compiling kernels test10 and upper?
Date: Fri, 10 Nov 2000 22:47:25 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205683@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205680@msgid-missing>
I am maintaining a stable compiler for the ia64-linux (formerly Trillian)
group. You can get it via ftp from ftp.cygnus.com in pub/ia64-linux.
This compiler assumes that you are using glibc 2.2. This is based on FSF
gcc snapshots from the July/August timeframe. There are patches to make
uit mostly work with glibc 2.1.3.
You can try using FSF gcc snapshots, but they tend to be a bit chaotic.
Especially so for ia64, because we are still doing optimization work on the
ia64 port, and hence we are occasionally destabilizing the ia64 port with
new optimizations.
Jim
next prev parent reply other threads:[~2000-11-10 22:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-10 11:14 [Linux-ia64] Recommended compiler for compiling kernels test10 and upper? Francis Galiegue
2000-11-10 14:17 ` Jes Sorensen
2000-11-10 14:49 ` [Linux-ia64] Recommended compiler for compiling kernels test10 Francis Galiegue
2000-11-10 22:47 ` Jim Wilson [this message]
2000-11-12 20:41 ` [Linux-ia64] Recommended compiler for compiling kernels test1 Pimenov, Sergei
2000-11-13 20:23 ` [Linux-ia64] Recommended compiler for compiling kernels Scott Hankin
2000-11-13 20:34 ` [Linux-ia64] Recommended compiler for compiling kernels test1 0 and upper? Jim Wilson
2000-11-13 20:38 ` [Linux-ia64] Recommended compiler for compiling kernels test1 Broadfoot, KenX
2000-11-13 20:52 ` [Linux-ia64] Recommended compiler for compiling kernels test1 0 and upper? H . J . Lu
2000-11-13 20:59 ` H . J . Lu
2000-11-13 21:14 ` Jim Wilson
2000-11-13 21:17 ` H . J . Lu
2000-11-13 21:19 ` [Linux-ia64] Recommended compiler for compiling kernels test10 " Jim Wilson
2000-11-13 21:23 ` [Linux-ia64] Recommended compiler for compiling kernels test1 0 " Jim Wilson
2000-11-13 21:38 ` [Linux-ia64] Recommended compiler for compiling kernels test10 " Gerrit Huizenga
2000-11-13 22:00 ` [Linux-ia64] Recommended compiler for compiling kernels Scott Hankin
2000-11-13 22:09 ` Scott Hankin
2000-11-13 22:10 ` [Linux-ia64] Recommended compiler for compiling kernels test1 0 and Jun Nakajima
2000-11-13 22:25 ` [Linux-ia64] Recommended compiler for compiling kernels test10 and upper? Gerrit Huizenga
2000-11-13 22:36 ` [Linux-ia64] Recommended compiler for compiling kernels Scott Hankin
2000-11-13 22:37 ` [Linux-ia64] Recommended compiler for compiling kernels test10 and upper? Jim Wilson
2000-11-13 22:44 ` [Linux-ia64] Recommended compiler for compiling kernels Scott Hankin
2000-11-13 23:01 ` [Linux-ia64] Recommended compiler for compiling kernels test10 and upper? Jim Wilson
2000-11-13 23:06 ` Gerrit Huizenga
2000-11-13 23:08 ` H . J . Lu
2000-11-13 23:14 ` Jim Wilson
2000-11-13 23:31 ` Don Dugger
2000-11-13 23:33 ` Jim Wilson
2000-11-14 0:24 ` Don Dugger
2000-11-15 17:59 ` [Linux-ia64] Recommended compiler for compiling kernels Scott Hankin
2000-11-15 19:52 ` [Linux-ia64] Recommended compiler for compiling kernels test10 and upper? Jim Wilson
2000-11-16 2:51 ` H . J . Lu
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=marc-linux-ia64-105590678205683@msgid-missing \
--to=wilson@cygnus.com \
--cc=linux-ia64@vger.kernel.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