From: Joe Buck <jbuck@synopsys.com>
To: jbuck@synopsys.com (Joe Buck)
Cc: kriol@fnal.gov, jbuck@synopsys.com, frichard@bbn.com, egcs@cygnus.com
Subject: Re: sparc64 support for Solaris
Date: Sat, 18 Oct 1997 12:39:00 -0000 [thread overview]
Message-ID: <199710181930.MAA05549@atrus.synopsys.com> (raw)
In-Reply-To: <199710181852.LAA05319@atrus.synopsys.com>
> > > Solaris 2.5.x does not save the 64-bit register state, so basically some
> > > registers will come back randomized (from other processes?).
> >
> > hmm...
> > are you sure ?
> > Solaris2.5.1 ultra != solaris 2.5.1 32bit sparc.
I said:
> I am quite certain.
That is, I am quite certain that there is a problem. I was not
certain (or correct) about the details.
Well, as has been pointed out, they are zero-extended, not random,
but the essense is that user-mode 64-bit code is unsafe.
next prev parent reply other threads:[~1997-10-18 12:39 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
1997-10-17 21:50 ` Oleg Krivosheev
1997-10-18 11:53 ` Joe Buck
1997-10-18 12:39 ` Joe Buck [this message]
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=199710181930.MAA05549@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=frichard@bbn.com \
--cc=kriol@fnal.gov \
/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).