All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Matthew Kirkwood <matthew@hairy.beasts.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.6: JFS vs gcc 2.95.4
Date: Sun, 10 Mar 2002 10:33:46 -0800	[thread overview]
Message-ID: <3C8BA70A.206C0EFE@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0203101600010.31738-100000@sphinx.mythic-beasts.com>

Matthew Kirkwood wrote:
> 
> Hi,
> 
> I can't build jfs in 2.5.6 with gcc 2.95.4 from Debian
> testing:
> 
> gcc -D__KERNEL__ -I/home/matthew/kern/linux-2.5.6/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> -march=k6  -D_JFS_4K -DKBUILD_BASENAME=jfs_imap  -c -o jfs_imap.o
> jfs_imap.c
> jfs_imap.c: In function `diAlloc':
> /home/matthew/kern/linux-2.5.6/include/asm/rwsem.h:169: inconsistent
> operand constraints in an `asm'
> jfs_imap.c: In function `diNewIAG':
> /home/matthew/kern/linux-2.5.6/include/asm/rwsem.h:169: inconsistent
> operand constraints in an `asm'
> 
> I don't really speak gcc asm, so I don't know where to start
> on this.  Is it a known issue?
> 

This worked for me:

--- linux-2.5.6/include/asm-i386/rwsem.h	Tue Feb 19 18:11:01 2002
+++ 25/include/asm-i386/rwsem.h	Sat Mar  9 14:37:35 2002
@@ -164,7 +164,7 @@ LOCK_PREFIX	"  xadd      %%edx,(%%eax)\n
 		"  jmp       1b\n"
 		LOCK_SECTION_END
 		"# ending __up_read\n"
-		: "+m"(sem->count), "+d"(tmp)
+		: /*"+m"(sem->count),*/ "+d"(tmp)
 		: "a"(sem)
 		: "memory", "cc");
 }

-

  reply	other threads:[~2002-03-10 18:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-10 16:01 2.5.6: JFS vs gcc 2.95.4 Matthew Kirkwood
2002-03-10 18:33 ` Andrew Morton [this message]
2002-03-10 19:15   ` Matthew Kirkwood
2002-03-10 19:24     ` Andrew Morton

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=3C8BA70A.206C0EFE@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@hairy.beasts.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.