public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: n0ano@indstorage.com
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] correct seg fault address on ia-64??
Date: Wed, 14 Nov 2001 18:02:37 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805512@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805506@msgid-missing>

Rich-

A while back someone from SCO made a presentation at one of the
early Intel Developer Forums about just this topic.  I can't
find it in a quick search of either the SCO (now Caldera) or
Intel sites.  Maybe someone from Caldera or Intel can see if
that presentation is still available.

On Wed, Nov 14, 2001 at 09:22:31AM -0800, Rich Altmaier wrote:
> Such horrible things are being done in source code in the 64bit
> environment.   Is there any kind of "porting guide" available?
> A long time ago we did a porting guide for MIPSPro, see
> 
>     http://techpubs.sgi.com/library/tpl/cgi-bin/init.cgi
>     in search enter:  mipspro 64-bit
>     and take a look at the MIPSpro 64-bit Porting and Transition Guide,
>     select Chapter 3, second portion (first portion is Fortran, second is C).
> 
> What is out there for gcc?
> Thanks, Rich
> 
> 
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@indstorage.com
Ph: 303/652-0870x117


  parent reply	other threads:[~2001-11-14 18:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 16:03 [Linux-ia64] correct seg fault address on ia-64?? Pereira, D LailaX E
2001-11-14 16:42 ` n0ano
2001-11-14 16:45 ` Andreas Schwab
2001-11-14 16:49 ` Dan Pop
2001-11-14 17:22 ` Rich Altmaier
2001-11-14 17:49 ` Christoph Hellwig
2001-11-14 18:02 ` n0ano [this message]
2001-11-14 18:51 ` Rok Sosic

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-105590698805512@msgid-missing \
    --to=n0ano@indstorage.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