public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Carr <jfc@tiac.net>
To: Joe Buck <jbuck@synopsys.com>
Cc: frichard@bbn.com, egcs@cygnus.com
Subject: Re: sparc64 support for Solaris
Date: Fri, 17 Oct 1997 19:44:00 -0000	[thread overview]
Message-ID: <199710180243.WAA02221@jfc.> (raw)
In-Reply-To: <199710180206.TAA24784@atrus.synopsys.com>

> > I was wondering how I can enable 64 bit support and v9 instruction
> > scheduling for an Ultra 1 Model 170 running Solaris2.5.
> 
> If you turned it on, your process would bomb at the first context switch.
> Solaris 2.5.x does not save the 64-bit register state, so basically some
> registers will come back randomized (from other processes?).

Not randomized, zero extended.

All 64 bits of the global and out registers are preserved over a
context switch.  I've made some changes to take advantage of this for
certain 64 bit operations in 32 bit mode (e.g. cmpdi is inline).  This
is effectively a peephole optimization -- I don't keep 64 bit registers
live across gcc instruction boundaries because that would be too hard.

> Solaris 2.6 is supposed to fix this.

2.6 is the same as 2.5, I'm told.  2.7 (next summer?) will support 64
bit processes.


  reply	other threads:[~1997-10-17 19:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-17 16:51 Fred Richardson
1997-10-17 19:03 ` David S. Miller
1997-10-17 19:06 ` Joe Buck
1997-10-17 19:44   ` John Carr [this message]
1997-10-17 21:50   ` Oleg Krivosheev
1997-10-18 11:53     ` Joe Buck
1997-10-18 12:39       ` Joe Buck
1997-10-17 19:31 Mike Stump
1997-10-19 13:06 ` Fred Richardson
1997-10-20 18:57   ` John Carr
1997-10-20 19:22   ` Doug Evans

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=199710180243.WAA02221@jfc. \
    --to=jfc@tiac.net \
    --cc=egcs@cygnus.com \
    --cc=frichard@bbn.com \
    --cc=jbuck@synopsys.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).