Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: linux-mips@oss.sgi.com
Subject: [PATCH] incorrect asm constraints for ll/sc constructs
Date: Wed, 23 May 2001 14:52:57 -0700	[thread overview]
Message-ID: <20010523145257.A13013@nevyn.them.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

The ll/sc constructs in the kernel use ".set noat" to inhibit use of $at,
and proceed to use it themselves.  This is fine, except for one problem: the
constraints on memory operands are "o" and "=o", which means offsettable
memory references.  If I'm not mistaken, the assembler will (always?)
turn these into uses of $at if the offset is not 0 - at least, it certainly
seems to do that here (gcc 2.95.3, binutils 2.10.91.0.2).  Just being honest
with the compiler and asking for a real memory reference does the trick. 
Does this patch look right?

-- 
Daniel Jacobowitz                           Debian GNU/Linux Developer
Monta Vista Software                              Debian Security Team

[-- Attachment #2: mips-offset.diff --]
[-- Type: text/plain, Size: 1172 bytes --]

Index: arch/mips/kernel/sysmips.c
===================================================================
RCS file: /cvs/linux/arch/mips/kernel/sysmips.c,v
retrieving revision 1.18
diff -u -r1.18 sysmips.c
--- arch/mips/kernel/sysmips.c	2001/04/08 13:24:27	1.18
+++ arch/mips/kernel/sysmips.c	2001/05/23 21:49:29
@@ -99,8 +99,8 @@
 			".word\t1b, 3b\n\t"
 			".word\t2b, 3b\n\t"
 			".previous\n\t"
-			: "=&r" (tmp), "=o" (* (u32 *) p), "=r" (errno)
-			: "r" (arg2), "o" (* (u32 *) p), "2" (errno)
+			: "=&r" (tmp), "=m" (* (u32 *) p), "=r" (errno)
+			: "r" (arg2), "m" (* (u32 *) p), "2" (errno)
 			: "$1");
 
 		if (errno)
Index: include/asm-mips/system.h
===================================================================
RCS file: /cvs/linux/include/asm-mips/system.h,v
retrieving revision 1.27
diff -u -r1.27 system.h
--- include/asm-mips/system.h	2001/03/28 01:35:12	1.27
+++ include/asm-mips/system.h	2001/05/23 21:49:29
@@ -219,8 +219,8 @@
 		" ll\t%0, %3\n\t"
 		".set\tat\n\t"
 		".set\treorder"
-		: "=r" (val), "=o" (*m), "=r" (dummy)
-		: "o" (*m), "2" (val)
+		: "=r" (val), "=m" (*m), "=r" (dummy)
+		: "m" (*m), "2" (val)
 		: "memory");
 
 	return val;

             reply	other threads:[~2001-05-23 21:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23 21:52 Daniel Jacobowitz [this message]
2001-05-24 13:42 ` [PATCH] incorrect asm constraints for ll/sc constructs Maciej W. Rozycki
2001-05-24 23:44   ` Daniel Jacobowitz
2001-05-25 13:13     ` Maciej W. Rozycki
2001-05-25 21:15       ` Kevin D. Kissell
2001-05-25 21:15         ` Kevin D. Kissell
2001-05-25 21:49         ` Daniel Jacobowitz
2001-05-26 22:14           ` Kevin D. Kissell
2001-05-26 22:14             ` Kevin D. Kissell
2001-05-26 22:23             ` Ralf Baechle
2001-05-28 11:20             ` Maciej W. Rozycki
2001-05-28 13:48               ` Kevin D. Kissell
2001-05-28 13:48                 ` Kevin D. Kissell
2001-05-28 13:59                 ` Maciej W. Rozycki
2001-05-25 20:27   ` Ralf Baechle
2001-05-25 20:49     ` Daniel Jacobowitz
2001-05-28 11:09       ` Maciej W. Rozycki
2001-05-30  0:17       ` Daniel Jacobowitz
2001-05-30  7:02         ` Kevin D. Kissell
2001-05-30  7:02           ` Kevin D. Kissell

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=20010523145257.A13013@nevyn.them.org \
    --to=dan@debian.org \
    --cc=linux-mips@oss.sgi.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