linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Holger Bettag <hobold@Informatik.Uni-Bremen.DE>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: CONFIG_ALTIVEC=y
Date: 24 May 2000 18:39:31 +0200	[thread overview]
Message-ID: <8xitw3ewcc.fsf@s63.informatik.uni-bremen.de> (raw)
In-Reply-To: Nicholas Coult's message of Tue, 23 May 2000 11:42:07 -0500 (CDT)


Nicholas Coult <coult@ima.umn.edu> writes:

>
> When a kernel is compiled with CONFIG_ALTIVEC=y, I assume this
> means that the kernel is aware of the Altivec registers, and keeps
> track of their contents during context switches?  And that code
> which uses Altivec instructions/registers will run properly with such
> a kernel?
>
Yes.

  Holger

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-05-24 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-23 16:42 CONFIG_ALTIVEC=y Nicholas Coult
2000-05-24 16:39 ` Holger Bettag [this message]
2000-05-24 16:59   ` CONFIG_ALTIVEC=y Giuliano Pochini

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=8xitw3ewcc.fsf@s63.informatik.uni-bremen.de \
    --to=hobold@informatik.uni-bremen.de \
    --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).