public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/6816] Support for POWER7 VSX registers in *context routines
Date: Wed, 15 Oct 2008 22:23:00 -0000 [thread overview]
Message-ID: <20081015222217.8201.qmail@sourceware.org> (raw)
In-Reply-To: <20080804175727.6816.cseo@linux.vnet.ibm.com>
------- Additional Comments From drepper at redhat dot com 2008-10-15 22:22 -------
I've asked this before but I don't remember getting a reply.
On x86/x86-64 the additional registers are not preserved in function calls.
This means the context functions don't have to handle the registers. The kernel
still provides the register content to signal handlers but that's a different story.
Why has the decision been made that the registers have to be saved (assuming
they are, otherwise the whole extension business is mood)?
--
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |WAITING
http://sourceware.org/bugzilla/show_bug.cgi?id=6816
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2008-10-15 22:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 17:58 [Bug libc/6816] New: " cseo at linux dot vnet dot ibm dot com
2008-08-04 18:17 ` [Bug libc/6816] " cseo at linux dot vnet dot ibm dot com
2008-08-04 18:17 ` cseo at linux dot vnet dot ibm dot com
2008-08-04 18:18 ` cseo at linux dot vnet dot ibm dot com
2008-08-04 18:19 ` cseo at linux dot vnet dot ibm dot com
2008-08-04 18:20 ` cseo at linux dot vnet dot ibm dot com
2008-08-05 15:40 ` rsa at us dot ibm dot com
2008-08-05 17:54 ` sjmunroe at us dot ibm dot com
2008-08-05 19:42 ` rsa at us dot ibm dot com
2008-08-25 22:55 ` drepper at redhat dot com
2008-09-12 21:59 ` cseo at linux dot vnet dot ibm dot com
2008-09-12 21:59 ` cseo at linux dot vnet dot ibm dot com
2008-09-12 22:00 ` cseo at linux dot vnet dot ibm dot com
2008-09-12 22:01 ` cseo at linux dot vnet dot ibm dot com
2008-09-12 22:02 ` cseo at linux dot vnet dot ibm dot com
2008-09-12 22:02 ` cseo at linux dot vnet dot ibm dot com
2008-09-12 22:03 ` cseo at linux dot vnet dot ibm dot com
2008-09-12 22:04 ` cseo at linux dot vnet dot ibm dot com
2008-09-12 22:16 ` cseo at linux dot vnet dot ibm dot com
2008-10-15 22:23 ` drepper at redhat dot com [this message]
2008-10-16 14:02 ` rsa at us dot ibm dot com
2008-10-16 14:57 ` drepper at redhat dot com
2008-10-16 16:54 ` sjmunroe at us dot ibm dot com
2008-10-16 17:07 ` drepper at redhat dot com
2008-10-16 19:38 ` sjmunroe at us dot ibm dot com
2009-04-07 18:10 ` drepper at redhat dot com
2009-04-07 18:31 ` rsa at us dot ibm dot com
2009-04-07 18:39 ` drepper at redhat dot com
2010-06-01 3:38 ` pasky at suse dot cz
2010-06-01 15:02 ` rsa at us dot ibm dot com
2010-06-01 15:40 ` rsa at us dot ibm dot com
[not found] <bug-6816-131@http.sourceware.org/bugzilla/>
2013-10-11 7:52 ` jakub at redhat dot com
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=20081015222217.8201.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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).