linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH v2 1/2] powerpc: Fix building of feature-fixup tests on ppc32
Date: Tue, 1 Jul 2008 10:16:16 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0807011015390.20129@blarg.am.freescale.net> (raw)

We need to use PPC_LCMPI otherwise we get compile errors like:

arch/powerpc/lib/feature-fixups-test.S: Assembler messages:
arch/powerpc/lib/feature-fixups-test.S:142: Error: Unrecognized opcode: `cmpdi'
arch/powerpc/lib/feature-fixups-test.S:149: Error: Unrecognized opcode: `cmpdi'
arch/powerpc/lib/feature-fixups-test.S:164: Error: Unrecognized opcode: `cmpdi'

Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
---
 arch/powerpc/lib/feature-fixups-test.S |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/powerpc/lib/feature-fixups-test.S b/arch/powerpc/lib/feature-fixups-test.S
index 10d038b..0549be0 100644
--- a/arch/powerpc/lib/feature-fixups-test.S
+++ b/arch/powerpc/lib/feature-fixups-test.S
@@ -139,14 +139,14 @@ globl(ftr_fixup_test6)
 1:	or	1,1,1
 BEGIN_FTR_SECTION
 	or	5,5,5
-2:	cmpdi	r3,0
+2:	PPC_LCMPI	r3,0
 	beq	4f
 	blt	2b
 	b	1b
 	b	4f
 FTR_SECTION_ELSE
 2:	or	2,2,2
-	cmpdi	r3,1
+	PPC_LCMPI	r3,1
 	beq	3f
 	blt	2b
 	b	3f
@@ -161,7 +161,7 @@ globl(end_ftr_fixup_test6)
 globl(ftr_fixup_test6_expected)
 1:	or	1,1,1
 2:	or	2,2,2
-	cmpdi	r3,1
+	PPC_LCMPI	r3,1
 	beq	3f
 	blt	2b
 	b	3f
-- 
1.5.5.1

             reply	other threads:[~2008-07-01 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01 15:16 Kumar Gala [this message]
2008-07-02  9:35 ` [PATCH v2 1/2] powerpc: Fix building of feature-fixup tests on ppc32 Michael Ellerman
2008-07-02 14:31   ` Kumar Gala
2008-07-02 23:31   ` Segher Boessenkool

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=Pine.LNX.4.64.0807011015390.20129@blarg.am.freescale.net \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).