All of lore.kernel.org
 help / color / mirror / Atom feed
From: Perry Wagle <wagle@wirex.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Distributions using gcc 3.2 or later
Date: Wed, 15 Jan 2003 17:43:39 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805681@msgid-missing> (raw)

Hi --

I need to test and improve modifications of GCC 3.2 or later on a IA64 
as part of a demonstration that those modifications aren't IA32 
specific.  As it is, I am just now showing that I can build entire 
production quality Linux distributions with my (currently non-standard) 
compilers on IA32, and I want to extend that to a couple more platforms.

Intel has graciously short-term-loaned me a IA64.  Before Christmas 
break, I poked around, and all the Linux distributions for IA64 seemed 
GCC 2.96 based, except for the Redhat rawhide distribution.  But, 
testing with alpha-test distributions makes me nervous that I would be 
testing much more than my changes.  Now that my compiler modification 
is starting to work, I thought I'd poke my head out and ask what 
distribution I should use that would expect GCC 3.2 or later?

Or perhaps, if you have a fork going in GCC for IA64, I should use it 
instead?  The purpose is to propose inclusion of my modifications into 
the GCC main branch.

-- Perry Wagle (wagle@wirex.com)



             reply	other threads:[~2003-01-15 17:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 17:43 Perry Wagle [this message]
2003-01-15 18:05 ` [Linux-ia64] Distributions using gcc 3.2 or later Martin Schimmer
2003-01-15 18:12 ` Randolph Chung
2003-01-15 18:15 ` David Mosberger
2003-01-15 18:26 ` Matthew Wilcox
2003-01-15 19:02 ` Gwenole Beauchesne
2003-01-15 19:12 ` n0ano
2003-01-15 19:35 ` Matthew Wilcox
2003-01-15 20:14 ` Wichmann, Mats D
2003-01-15 21:44 ` Grant Grundler

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-105590709805681@msgid-missing \
    --to=wagle@wirex.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.