public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: jsiegel@mvista.com
Cc: linux-kernel@vger.kernel.org, linuxsh-dev@lists.sourceforge.net
Subject: Re: [PATCH] Preemptible kernel for SH
Date: 05 Dec 2001 17:22:27 -0500	[thread overview]
Message-ID: <1007590948.28563.8.camel@phantasy> (raw)
In-Reply-To: <1007261428.820.4.camel@phantasy>
In-Reply-To: <1007261428.820.4.camel@phantasy>

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

Users of gcc-3.x will need the attached patch _for gcc_ to compile an SH
kernel patched with preempt-kernel.  This is _not_ our fault, it is a
gcc bug and is now merged into CVS and should be part of gcc-3.1.

gcc-2.9x compiles without problem.  It is only 3.x versions that suffer
the bug.

	Robert Love

P.S. Also of note: yes this works on Sega Dreamcast.  You can have a
fully preemptible Dreamcast.  Impress your friends.  Or something.

[-- Attachment #2: gcc-ice-rml-3.0.2-1.patch --]
[-- Type: text/plain, Size: 682 bytes --]

--- gcc/gcc/alias.c	2001/09/11 21:39:24	1.115.4.7
+++ gcc/gcc/alias.c	2001/11/18 08:16:38	1.115.4.8
@@ -1041,6 +1041,9 @@
   /* Some RTL can be compared without a recursive examination.  */
   switch (code)
     {
+    case VALUE:
+     return CSELIB_VAL_PTR (x) == CSELIB_VAL_PTR (y);
+
     case REG:
       return REGNO (x) == REGNO (y);
 
@@ -1109,6 +1112,12 @@
 	  if (rtx_equal_for_memref_p (XEXP (x, i), XEXP (y, i)) == 0)
 	    return 0;
 	  break;
+
+	  /* This can happen for asm operands.  */
+	case 's':
+	  if (strcmp (XSTR (x, i), XSTR (y, i)))
+	    return 0;
+	break;
 
 	/* This can happen for an asm which clobbers memory.  */
 	case '0':

      parent reply	other threads:[~2001-12-05 22:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-02  2:50 [PATCH] Preemptible kernel for SH Robert Love
2001-12-02  3:28 ` Robert Love
2001-12-03 21:16 ` [linuxsh-dev] " Jeremy Siegel
2001-12-03 22:18   ` Robert Love
2001-12-05 22:22 ` Robert Love [this message]

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=1007590948.28563.8.camel@phantasy \
    --to=rml@tech9.net \
    --cc=jsiegel@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxsh-dev@lists.sourceforge.net \
    /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