From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] unalinged access by loadpair instruction
Date: Mon, 09 Dec 2002 21:41:36 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805526@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805518@msgid-missing>
It looks to me like getfpreg() and setfpreg() are pretty obviously
broken: they doesn't take rotation into account at all. Seems this
was missed when the integer-side was fixed (by Tony, IIRC). Anyone
want to take a shot at fixing this?
--david
>>>>> On Mon, 09 Dec 2002 23:28:45 +0900, "Hideki Yamamoto" <hideki@hpc.bs1.fc.nec.co.jp> said:
Hideki> Hi everyone,
Hideki> When unaligned access is happened by loadpair instruction,
Hideki> reloading by kernel is wrong.
Hideki> When unalined access is happeded by loadpair instruction in
Hideki> NORMAL loop, it is no problem. Please try to run the
Hideki> attached programs(c.c and a.s) compiled by gcc.
Hideki> However, When it is happned by loadpair instruction in SWP
Hideki> loop, it fails to reload the data. Please try to run the
Hideki> attached programs(c.c and aa.s) compiled by gcc. aa.s is
Hideki> included loadpair in SWP loop. If there is no happening,
Hideki> please change the n parameter to bigger number.
Hideki> Sorry, I could not isolate whether or not it is caused by
Hideki> HW bug or Kernel problem.
Hideki> Let me know somebody understood the cause why it is
Hideki> happened.
next prev parent reply other threads:[~2002-12-09 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 14:28 [Linux-ia64] unalinged access by loadpair instruction Hideki Yamamoto
2002-12-09 21:41 ` David Mosberger [this message]
2002-12-09 22:59 ` Luck, Tony
2002-12-10 2:33 ` David Mosberger
2002-12-10 11:12 ` Hideki Yamamoto
2002-12-10 12:18 `
2002-12-11 7:26 ` Hideki Yamamoto
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-105590709805526@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox