From: Giuliano Pochini <pochini@denise.shiny.it>
To: Adrian Cox <apc@agelectronics.co.uk>
Cc: Rob Barris <rbarris@quicksilver.com>,
LinuxPPC-Dev <linuxppc-dev@lists.linuxppc.org>,
Debian PowerPC <debian-powerpc@lists.debian.org>
Subject: Re: Altivec and binary compatibility
Date: Sun, 20 Feb 2000 11:00:13 -0500 [thread overview]
Message-ID: <38B00F8D.CEE8CAFF@denise.shiny.it> (raw)
In-Reply-To: 38A7D0FD.D6A7E95D@agelectronics.co.uk
> > This is not correct. OS's on P-III have to be updated to provide proper
> > context switch support for the SSE registers. I'm pretty sure Win98 has it
> > covered. It's really the same type of jump as AltiVec - use of SSE
> > features is not restricted to OS or driver code, apps use them too.
>
> I know that the OS has to support these registers. Latest development
> kernels *DO* support them.
>
> That is not the problem.
>
> The problem is with C++ exception sequences and setjmp being different
> for Altivec and non-Altivec code.
IMHO C++ exceptions are not a problem. All objects are destroyed when a
function exits with an exception and it's an exit without return. The thrown
object is put on the stack (I think) and the calling code will handle it.
Obviously you can't mix code compiled for Altivec and code compiled for plain
PPC if they exchange data with exceptions, jumps and friends.
> How does Linux on ia32 handle linking between generic ia32 and Pentium-III user-space code ?
No idea... It's likely an unsolved issue yet.
Bye.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-02-20 16:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-04 10:29 Altivec and binary compatibility Adrian Cox
2000-02-07 15:11 ` Giuliano Pochini
2000-02-07 18:06 ` Adrian Cox
2000-02-08 20:11 ` Giuliano Pochini
2000-02-11 9:41 ` Adrian Cox
[not found] ` <v03010d02b4cce4346bac@[192.168.1.16]>
[not found] ` <38A7D0FD.D6A7E95D@agelectronics.co.uk>
2000-02-20 1:18 ` Giuliano Pochini
2000-02-20 16:00 ` Giuliano Pochini [this message]
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=38B00F8D.CEE8CAFF@denise.shiny.it \
--to=pochini@denise.shiny.it \
--cc=apc@agelectronics.co.uk \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rbarris@quicksilver.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 NNTP newsgroup(s).