All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] sigaltstack and ar.bspstore
Date: Fri, 30 May 2003 16:32:03 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723706088@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723706086@msgid-missing>

>>>>> On Sat, 31 May 2003 00:18:39 +1000, Matt Chapman <matthewc@cse.unsw.edu.au> said:

  Matt> Presumably the result should be the same as the original
  Matt> bspstore.  However, it isn't in the case when the original
  Matt> bspstore is pointing to slot 63 (the RNAT word).  The new
  Matt> bspstore comes out pointing to slot 0 of the next group, and
  Matt> the RNAT bits never get written.  This happens more often then
  Matt> you'd expect, since it seems that current implementations make
  Matt> the optimisation of writing the RNAT word together with the
  Matt> first word of the new group instead of the last word of the
  Matt> old group (sensible because it potentially saves a write).

Yes, I noticed the same in libunwind. ;-/

  Matt> I'd propose that the trampoline code should save bspstore in
  Matt> the sigcontext structure and restore it from there rather than
  Matt> recalculating it.  I can send a patch, but first is there any
  Matt> reason why it shouldn't be done that way?

My preference would be to fix it in a way that preserves binary
compatibility for the sigcontext structure.

	--david


  reply	other threads:[~2003-05-30 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 14:18 [Linux-ia64] sigaltstack and ar.bspstore Matt Chapman
2003-05-30 16:32 ` David Mosberger [this message]
2003-05-31  1:31 ` Matt Chapman
2003-05-31  3:16 ` David Mosberger
2003-06-21  6:05 ` David Mosberger
2003-06-21  6:58 ` Matt Chapman
2003-06-23 19:16 ` David Mosberger

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=marc-linux-ia64-105590723706088@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.