From: Finn Thain <fthain@telegraphics.com.au>
To: "Mattias Engdegård" <mattiase@bredband.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org, zippel@linux-m68k.org
Subject: Re: FPU emulation incorrect for 68LC040?
Date: Thu, 22 Jul 2010 11:05:42 +1000 (EST) [thread overview]
Message-ID: <alpine.OSX.2.00.1007221056390.354@localhost> (raw)
In-Reply-To: <41EF646C-8866-4070-B772-94E39EF4620B@bredband.net>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 966 bytes --]
On Wed, 21 Jul 2010, Mattias Engdegård wrote:
> 21 jul 2010 kl. 22.32 skrev Geert Uytterhoeven:
>
> > As the 'LC040 doesn't implement FPU instructions, I'd expect it to
> > just generate an exception when the "fadd.d (a0)+,fp0" is encountered.
> > I.e. not do anything else, like postincrementing a0.
>
> According to the manual, it generates a special 8-word exception frame
> that contains the decoded effective address, as a help to the emulator.
> It only makes sense if the user can just use that EA right away (after
> having established that it is a memory operand). I suppose the only way
> to find out is to find someone with a genuine 'LC040 (a non-buggy one).
I have both kinds, buggy and non-buggy. Unfortunately, these machines
(PowerBooks) don't have working SCSI and the one with IDE has no Linux
filesystem.
But if you send me some inline asm, I'll patch it into busybox and test a
2.6.34 initramfs for you.
Finn
next prev parent reply other threads:[~2010-07-22 1:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 20:22 FPU emulation incorrect for 68LC040? Mattias Engdegård
2010-07-21 20:32 ` Geert Uytterhoeven
2010-07-21 20:53 ` Mattias Engdegård
2010-07-22 1:05 ` Finn Thain [this message]
2010-07-22 19:55 ` Mattias Engdegård
2010-07-23 4:12 ` Finn Thain
2010-07-23 8:39 ` Mattias Engdegård
2010-07-24 0:31 ` Michael Schmitz
2010-07-24 18:33 ` Mattias Engdegård
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=alpine.OSX.2.00.1007221056390.354@localhost \
--to=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=mattiase@bredband.net \
--cc=zippel@linux-m68k.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