From: Siarhei Siamashka <siarhei.siamashka@gmail.com>
To: "DebBarma, Tarun Kanti" <tarun.kanti@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM:VFPv3:enable {d16-d31} access
Date: Tue, 25 May 2010 15:26:51 +0300 [thread overview]
Message-ID: <201005251526.52041.siarhei.siamashka@gmail.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB0322FA884E@dbde02.ent.ti.com>
On Tuesday 25 May 2010, DebBarma, Tarun Kanti wrote:
> (Including ARM mailing list)
>
> From: Tarun Kanti Debbarma <a0876346@a0876346-desktop.(none)>
>
> This patch attempts to fix two related problems:
>
> (1) vfp_get_double(), vfp_put_double() functions have VFPv3 specific
> implementation guarded within CONFIG_VFPv3 macro. The intent is to access
> {d16-d31} additional registers provided in VFPv3. However, it still wrongly
> refers to {d0-d15}. This has been corrected.
This does not seem to be the case, see below.
> (2) While compiling the above changes, it produced compilation error
> because arch/arm/vfp/Makefile had the -mfpu=vfp option which could not
> recognize VFPv3 registers. This has been corrected to -mfpu=vfp3. With this
> option we are also able to compile pre-VFPv3 code.
>
> Signed-off-by: Tarun Kanti Debbarma <tarun.kanti@ti.com>
> ---
> arch/arm/vfp/Makefile | 2 +-
> arch/arm/vfp/vfphw.S | 8 ++++----
> 2 files changed, 5 insertions(+), 5 deletions(-)
> mode change 100644 => 100755 arch/arm/vfp/vfphw.S
>
> diff --git a/arch/arm/vfp/Makefile b/arch/arm/vfp/Makefile
> index 39f6d8e..75855c0 100644
> --- a/arch/arm/vfp/Makefile
> +++ b/arch/arm/vfp/Makefile
> @@ -7,7 +7,7 @@
> # EXTRA_CFLAGS := -DDEBUG
> # EXTRA_AFLAGS := -DDEBUG
>
> -KBUILD_AFLAGS :=$(KBUILD_AFLAGS:-msoft-float=-Wa,-mfpu=softvfp+vfp)
> +KBUILD_AFLAGS :=$(KBUILD_AFLAGS:-msoft-float=-Wa,-mfpu=vfp3
> -mfloat-abi=softfp) LDFLAGS +=--no-warn-mismatch
>
> obj-y += vfp.o
> diff --git a/arch/arm/vfp/vfphw.S b/arch/arm/vfp/vfphw.S
> old mode 100644
> new mode 100755
> index 66dc2d0..b034076
> --- a/arch/arm/vfp/vfphw.S
> +++ b/arch/arm/vfp/vfphw.S
> @@ -254,8 +254,8 @@ ENTRY(vfp_get_double)
> .endr
> #ifdef CONFIG_VFPv3
> @ d16 - d31 registers
> - .irp dr,0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
> -1: mrrc p11, 3, r0, r1, c\dr @ fmrrd r0, r1, d\dr
> + .irp dr,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31
> +1: fmrrd r0, r1, d\dr
The existing code does exactly the same, but avoids the need to
specify -mfpu=vfp3 option. It's quite easy to verify:
/**** test.S *******/
test:
mrrc p11, 3, r0, r1, c0
fmrrd r0, r1, d16
/*******************/
gcc -c test.S
objdump -d test.o
Disassembly of section .text:
00000000 <test>:
0: ec510b30 vmov r0, r1, d16
4: ec510b30 vmov r0, r1, d16
The comment in the existing code is a bit misleading though.
--
Best regards,
Siarhei Siamashka
next prev parent reply other threads:[~2010-05-25 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Tarun Kanti DebBarma <tarun.kanti@ti.com>
2010-05-25 20:18 ` [PATCH] ARM:VFPv3:enable {d16-d31} access Tarun Kanti DebBarma
2010-05-25 9:09 ` DebBarma, Tarun Kanti
2010-05-25 12:26 ` Siarhei Siamashka [this message]
2010-05-25 15:43 ` DebBarma, Tarun Kanti
2010-05-25 18:57 ` Russell King - ARM Linux
2010-05-26 11:43 ` DebBarma, Tarun Kanti
2010-05-26 20:10 ` Russell King - ARM Linux
2010-05-27 4:37 ` DebBarma, Tarun Kanti
2010-05-27 9:29 ` Russell King - ARM Linux
2010-05-27 9:31 ` DebBarma, Tarun Kanti
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=201005251526.52041.siarhei.siamashka@gmail.com \
--to=siarhei.siamashka@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tarun.kanti@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).