All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly3.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org, dave.anglin@nrc-cnrc.gc.ca
Subject: Re: [parisc-linux] Re: [glibc] fixing delayed exceptions in hppa
Date: Sat, 23 Aug 2003 01:55:06 -0400	[thread overview]
Message-ID: <20030823055506.GA9821@systemhalted> (raw)
In-Reply-To: <200308222024.QAA16264@hiauly3.hia.nrc.ca>

On Fri, Aug 22, 2003 at 04:24:19PM -0400, John David Anglin wrote:
> Based on what Jim Hull said, I believe that would be better.  I was using
> 
>   "fldd 0(%%sr0,%%sp),%0" : "=f" (d) : "0" (d)
> 
> There isn't a true dependency in the above but I believe that any load
> to the destination register will raise the exception.

Dave, I'm sorry if you sent me a patch and I dropped it :( Did I ever
receive a diff for this from you?

It's rather vague at times because the spec says "or an operation which
depends on a pending, trapping insn." I think DHD, and perhaps myself
got caught up on the "load or store" which probably means only
register->memory (memory->register too) and not register->register.

I'll rewrite this patch to do an fldd and see what the tests say. I'm
toatally under the assumption that this operation doesn't need to be
optimal :) (e.g. If you use feraiseexcept a lot you are not a
high-performance program).

c.

  reply	other threads:[~2003-08-23  5:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-22  1:39 [parisc-linux] [glibc] fixing delayed exceptions in hppa Carlos O'Donell
2003-08-22  2:42 ` Matthew Wilcox
2003-08-22  3:04 ` [parisc-linux] " John David Anglin
2003-08-22 14:46   ` Carlos O'Donell
2003-08-22 20:24     ` John David Anglin
2003-08-23  5:55       ` Carlos O'Donell [this message]
2003-08-23 16:12         ` John David Anglin
2003-08-30 16:37           ` Carlos O'Donell
2003-08-30 22:54             ` John David Anglin

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=20030823055506.GA9821@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    --cc=dave@hiauly3.hia.nrc.ca \
    --cc=parisc-linux@lists.parisc-linux.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.