From: Jim Terman <terman@ddi.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: altivec instructions
Date: Mon, 24 Jan 2000 10:52:59 -0800 (PST) [thread overview]
Message-ID: <200001241852.KAA04045@sade.ddi.com> (raw)
We are trying to run a program that contains altivec instructions on a G4,
but the process keeps crashing (gdb will actually cause a kernal panic).
It looks like a bit in the MSR needs to be set. What would be the best
way to modify the kernel to let this happen?
--
______________________________________________________________________________
Jim Terman | 323 Vintage Park Dr. | Voice: (650) 356-5446
terman@ddi.com | Foster City, CA | Fax: (650) 356-5490
Diab-SDS, Inc. | 94404 | web site - http://www.ddi.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-01-24 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-24 18:52 Jim Terman [this message]
2000-01-24 21:32 ` altivec instructions Tony Mantler
2000-01-24 22:16 ` Robert Neugebauer
2000-01-24 23:32 ` Tony Mantler
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=200001241852.KAA04045@sade.ddi.com \
--to=terman@ddi.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).