public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: egcs@cygnus.com
Subject: Re: porting EGCS to the Cray T3E
Date: Wed, 15 Jul 1998 12:46:00 -0000	[thread overview]
Message-ID: <9807151941.AA20335@moene.indiv.nluug.nl> (raw)
In-Reply-To: <9807141802.AA04356@moene.indiv.nluug.nl>

I wrote:

>  A T3E is just a bunch of 21164 Alpha's interconnected in
>  an interesting way.  If the C library on the system is
>  not really botched up beyond repair, it shouldn't be
>  impossible to create an alphaev5-unicosmk-cray target.
>  However, this is about as much as I know about this topic,
>  so people with more info are kindly requested to step
>  forward.

As pointed out by Martin Knoblauch <knobi@rocketmail.com>, it  
should be alphaev5-cray-unicosmk, and as Julian C. Cummings  
<julianc@acl.lanl.gov> pointed out, the assembly language on the  
Cray is different from that on Digital Unix and the Free Unixen that  
have an Alpha port.  In fact, even though I only spent a few hours  
on a T3E January last year - and didn't have time to dig into the  
assembly language outcome of my compiles - I wouldn't be surprised [  
given previous experience with products from Mr. Cray ] that

	mulf	$f21, $f22, $f23

should be encoded as

	FX23	X21*X22

and

	shl	$11, $12, $13

as

	BA13	A11<A12

:-)

Some more serious observations vis-a-vis the T3E (all IIRC):

1. The operating system is micro-kernel based, but it's UNICOS (the
   vector computer's OS) compatible, i.e. it has a SYSV
   attitude^H^H^H^H^H^Hpersonality.

2. The T3E has a single global address space.  This means that any
   processing element can access (read/write) the memory belonging
   to any other PE; the necessary physical transfer of data is
   handled by the interconnect.  I think I recall (!) that the global
   addressing is accomplished by encoding the PE number in the upper 
   bits of the address.

   [ Whadusay ?  Virtual memory ?  Hah, I could quote Seymour
     Cray's opinion on virtual memory here, but this is a decent
     mailing list without explicit adult material, so I'll refrain ]

3. Last but not least, the Alpha's inside a T3E are operated in
   big-endian mode.  Little-endian is for peecee's (it's not called
   *little*-endian for nothing).

Hope this helps,
Toon.

  reply	other threads:[~1998-07-15 12:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-13 16:44 Julian C. Cummings
1998-07-13 23:48 ` Jeffrey A Law
1998-07-14 12:50   ` Toon Moene
1998-07-15 12:46     ` Toon Moene [this message]
1998-07-14  7:16 Martin Knoblauch
1998-07-14 11:29 Julian C. Cummings
1998-07-14 11:29 ` Jeffrey A Law
     [not found]   ` <law@hurl.cygnus.com>
1998-07-14 14:29     ` Julian C. Cummings
1998-07-14 13:20       ` Jeffrey A Law
1998-07-14 16:57     ` Julian C. Cummings
1998-07-14 14:29       ` Jeffrey A Law
1998-07-14 12:50 Benjamin Redelings I
1998-07-14 14:29 Julian C. Cummings
1998-07-16  0:32 Martin Knoblauch
1998-07-16 12:45 ` Toon Moene

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=9807151941.AA20335@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=egcs@cygnus.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 read-only IMAP folder(s) and NNTP newsgroup(s).