linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
To: linux-kernel@vger.kernel.org
Cc: trivial@rustcorp.com.au
Subject: [PATCH] 2.4.18/2.5.39 include/asm-alpha/mmu_context.h compile fix
Date: 28 Sep 2002 01:21:29 +0200	[thread overview]
Message-ID: <87smzv3tom.fsf@student.uni-tuebingen.de> (raw)

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

Hi,

CVS gcc doesn't allow mentioning __asm__("...") registers in the
clobber list any more (see also
http://gcc.gnu.org/ml/gcc/2002-09/msg00741.html).  This patch applies
to both 2.4.18 and 2.5.39.

-- 
	Falk


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: reload_thread.patch --]
[-- Type: text/x-patch, Size: 853 bytes --]

--- linux-2.5.39/include/asm-alpha/mmu_context.h~	2002-09-27 23:49:55.000000000 +0200
+++ linux-2.5.39/include/asm-alpha/mmu_context.h	2002-09-28 00:47:28.000000000 +0200
@@ -25,23 +25,23 @@
 extern inline unsigned long
 __reload_thread(struct pcb_struct *pcb)
 {
 	register unsigned long a0 __asm__("$16");
 	register unsigned long v0 __asm__("$0");
 
 	a0 = virt_to_phys(pcb);
 	__asm__ __volatile__(
 		"call_pal %2 #__reload_thread"
 		: "=r"(v0), "=r"(a0)
 		: "i"(PAL_swpctx), "r"(a0)
-		: "$1", "$16", "$22", "$23", "$24", "$25");
+		: "$1", "$22", "$23", "$24", "$25");
 
 	return v0;
 }
 
 
 /*
  * The maximum ASN's the processor supports.  On the EV4 this is 63
  * but the PAL-code doesn't actually use this information.  On the
  * EV5 this is 127, and EV6 has 255.
  *
  * On the EV4, the ASNs are more-or-less useless anyway, as they are

                 reply	other threads:[~2002-09-27 23:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87smzv3tom.fsf@student.uni-tuebingen.de \
    --to=falk.hueffner@student.uni-tuebingen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@rustcorp.com.au \
    /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).