From: James Hogan <james.hogan@imgtec.com>
To: Paul Burton <paul.burton@imgtec.com>, <linux-mips@linux-mips.org>
Subject: Re: [PATCH 04/11] MIPS: wrap cfcmsa & ctcmsa accesses for toolchains with MSA support
Date: Wed, 24 Sep 2014 13:08:20 +0100 [thread overview]
Message-ID: <5422B434.2020405@imgtec.com> (raw)
In-Reply-To: <1411551942-11153-5-git-send-email-paul.burton@imgtec.com>
On 24/09/14 10:45, Paul Burton wrote:
> and provide
> implementations for the TOOLCHAIN_SUPPORTS_MSA case which ".set msa" as
> appropriate.
nit: which *uses* ".set msa"?
Cheers
James
WARNING: multiple messages have this Message-ID (diff)
From: James Hogan <james.hogan@imgtec.com>
To: Paul Burton <paul.burton@imgtec.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH 04/11] MIPS: wrap cfcmsa & ctcmsa accesses for toolchains with MSA support
Date: Wed, 24 Sep 2014 13:08:20 +0100 [thread overview]
Message-ID: <5422B434.2020405@imgtec.com> (raw)
Message-ID: <20140924120820.Gj56QHZ4UEtZPa0SmoEvgIWdbh0qVphUG4V9ppczNIE@z> (raw)
In-Reply-To: <1411551942-11153-5-git-send-email-paul.burton@imgtec.com>
On 24/09/14 10:45, Paul Burton wrote:
> and provide
> implementations for the TOOLCHAIN_SUPPORTS_MSA case which ".set msa" as
> appropriate.
nit: which *uses* ".set msa"?
Cheers
James
next prev parent reply other threads:[~2014-09-24 12:08 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 9:45 [PATCH 00/11] FP/MSA fixes Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-09-24 9:45 ` [PATCH 01/11] MIPS: push .set arch=r4000 into the functions needing it Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-11-11 14:19 ` Ralf Baechle
2014-09-24 9:45 ` [PATCH 02/11] MIPS: assume at as source/dest of MSA copy/insert instructions Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-09-24 9:45 ` [PATCH 03/11] MIPS: remove MSA macro recursion Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-09-24 9:45 ` [PATCH 04/11] MIPS: wrap cfcmsa & ctcmsa accesses for toolchains with MSA support Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-09-24 12:08 ` James Hogan [this message]
2014-09-24 12:08 ` James Hogan
2014-09-25 9:23 ` Paul Burton
2014-09-25 9:23 ` Paul Burton
2014-09-25 10:24 ` James Hogan
2014-09-25 10:24 ` James Hogan
2014-09-24 9:45 ` [PATCH 05/11] MIPS: clear MSACSR cause bits when handling MSA FP exception Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-09-24 11:10 ` Sergei Shtylyov
2014-09-25 9:20 ` [PATCH v2 " Paul Burton
2014-09-25 9:20 ` Paul Burton
2014-09-24 9:45 ` [PATCH 06/11] MIPS: fix mfc1 & mfhc1 emulation for mips64 systems Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-09-24 9:45 ` [PATCH 07/11] MIPS: ensure FCSR cause bits are clear after invoking FPU emulator Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-09-24 9:45 ` [PATCH 08/11] MIPS: prevent FP context set via ptrace being discarded Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-09-24 9:45 ` [PATCH 09/11] MIPS: disable FPU if the mode is unsupported Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-09-24 9:45 ` [PATCH 10/11] Revert "MIPS: Don't assume 64-bit FP registers for context switch" Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-09-24 9:45 ` [PATCH 11/11] MIPS: MSA: Fix big-endian FPR_IDX implementation Paul Burton
2014-09-24 9:45 ` Paul Burton
2014-09-24 13:00 ` [PATCH 00/11] FP/MSA fixes James Hogan
2014-09-24 13:00 ` James Hogan
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=5422B434.2020405@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.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.