public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Pop <Dan.Pop@cern.ch>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: Fault 26?
Date: Thu, 07 Dec 2000 04:32:41 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205805@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205793@msgid-missing>


On Wed, 6 Dec 2000, Bill Nottingham wrote:

> David Mosberger (davidm@hpl.hp.com) said: 
> >   Bill> What is fault type 26?  I'm getting a few of these recently.
> > 
> > It's the "NaT consumption fault".  Either buggy code is trying to eat
> > a NaT value or something else goes wrong and a NaT value is created
> > when it shouldn't be.
> 
> It's happening in strcpy(), of all places, with two seemingly valid
> arguments.

Here's a patch that should fix it.  The bug was in a recovery code
that was highly unlikely to be ever executed, hence it passed
unnoticed for so long :-)

2000-12-07  Dan Pop  <Dan.Pop@cern.ch>

        * sysdeps/ia64/strcpy.S: fix a bug in a recovery code sequence


--- strcpy.S.old	Thu Dec  7 05:10:17 2000
+++ strcpy.S	Thu Dec  7 05:11:20 2000
@@ -120,7 +120,7 @@
 	br.ret.sptk.many b0
 .recovery2:
 	add	tmp = -8, asrc ;;
-	ld8	r[MEMLAT] = [tmp]
+	ld8	r[0] = [tmp]
 	br.cond.sptk .back2
 .recovery3:
 	add	tmp = -(MEMLAT + 1) * 8, src ;;


Thanks to David Mosberger for investigating the problem.

Dan



  parent reply	other threads:[~2000-12-07  4:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-05 22:23 [Linux-ia64] Re: Fault 26? Bill Nottingham
2000-12-06 22:18 ` Bill Nottingham
2000-12-07  4:32 ` Dan Pop [this message]
2000-12-07  4:41 ` David Mosberger
2000-12-08 17:53 ` Jes Sorensen

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-105590678205805@msgid-missing \
    --to=dan.pop@cern.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox