From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jonas Gorski <jonas.gorski@gmail.com>,
linux-mips@linux-mips.org, loongson-dev@googlegroups.com
Subject: Re: [PATCH] MIPS: Add emulation for fpureg-mem unaligned access
Date: Sun, 17 Jun 2012 11:09:43 +0200 [thread overview]
Message-ID: <20120617090943.GA29077@alpha.franken.de> (raw)
In-Reply-To: <20120616125847.GR2039@vicerveza.homeunix.net>
On Sat, Jun 16, 2012 at 02:58:47PM +0200, Lluís Batlle i Rossell wrote:
> Hello again,
>
> On Sat, Jun 16, 2012 at 02:15:13PM +0200, Lluís Batlle i Rossell wrote:
> > > From what I can tell, ldc1 is a valid MIPS32 instruction, so this
> > > should probably be something like
> > >
> > > case ld_op:
> > > #ifndef CONFIG_64BIT
> > > return sigill;
> > > #endif
> >
> > I agree! I'll repost with these fixes.
>
> Well, I think I take my words back. Handling the ldc1/sdc1 cases in MIPS32 is
> tricker than I thought first, because I can't use ldl/ldr or sdl/sdr there.
> Given my ability with mips assembly, I leave the patch as is.
>
> In 'patchwork' I had set the patch first to superseeded, but then I set it back
> to New.
why is there a reason for this ? Unaligned FPU access shouts to me simply
broken code, go fix that. But maybe I'm wrong ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2012-06-17 9:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 22:22 [PATCH] MIPS: Add emulation for fpureg-mem unaligned access Lluis Batlle i Rossell
2012-06-16 11:21 ` Jonas Gorski
2012-06-16 12:15 ` Lluís Batlle i Rossell
2012-06-16 12:40 ` [loongson-dev] " Lluís Batlle i Rossell
2012-06-20 19:05 ` Lluís Batlle i Rossell
2012-07-11 0:05 ` Maciej W. Rozycki
2012-07-30 19:47 ` Lluís Batlle i Rossell
2012-07-30 23:56 ` Maciej W. Rozycki
2012-06-16 12:58 ` Lluís Batlle i Rossell
2012-06-17 9:09 ` Thomas Bogendoerfer [this message]
2012-07-31 13:40 ` Ralf Baechle
2012-07-31 14:07 ` Lluís Batlle i Rossell
2012-07-31 15:10 ` Ralf Baechle
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=20120617090943.GA29077@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=jonas.gorski@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=loongson-dev@googlegroups.com \
/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.