From: Keith Owens <kaos@ocs.com.au>
To: Jack Steiner <steiner@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] /proc/ksyms change for IA64
Date: Thu, 02 Aug 2001 23:25:34 +1000 [thread overview]
Message-ID: <6048.996758734@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Thu, 02 Aug 2001 07:42:45 EST." <200108021242.HAA02573@fsgi055.americas.sgi.com>
On Thu, 2 Aug 2001 07:42:45 -0500 (CDT),
Jack Steiner <steiner@sgi.com> wrote:
>What problems exist with cross compiling.
>We are still using the cross-compiler for all of our building & testing.
>We use:
> gcc version 2.96-ia64-000717 snap 001117 (plus some patches that Ralf added last Dec).
>
>I know that at some point we need to convert to native builds but right now we
>dont have sufficient bigsur/lion boxes to do that.
>
>We have not seen any problems with the compiler we are using - at least we
>have not attributed a problem to the compiler.
The changes to the copy_user pipeline code in the latest 2.4.7-ia64
patch break snap 001117 in some circumstances. There are workarounds
but they require changes to code that is not IA64 related, not
satisfactory.
>Should we upgrade to gcc3.0 yet???
I have not succeeded building a cross compiler ix86 to ia64 for gcc
3.0, using a current CVS tree. The flow insn code breaks on some type
conversions in cross compile mode, even when using gcc 3.0 as the base
compiler. Debugging is still in progress.
next prev parent reply other threads:[~2001-08-02 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22393.996723520@kao2.melbourne.sgi.com>
2001-08-02 12:42 ` [Linux-ia64] [RFC] /proc/ksyms change for IA64 (fwd) Jack Steiner
2001-08-02 13:25 ` Keith Owens [this message]
2001-08-10 15:31 ` Jes Sorensen
2001-08-02 3:22 [RFC] /proc/ksyms change for IA64 Keith Owens
2001-08-05 5:44 ` Rusty Russell
2001-08-05 7:16 ` Keith Owens
2001-08-05 14:02 ` Rusty Russell
2001-08-05 14:51 ` Keith Owens
2001-08-19 1:27 ` Richard Henderson
2001-08-21 6:53 ` Keith Owens
2001-08-21 17:47 ` Richard Henderson
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=6048.996758734@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
/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 NNTP newsgroup(s).