Re: Linux 2.4.4-ac3, asm problem in asm-i386/rwsem.h using gcc 3.0 CVS

From: Mike Black (mblack@csihq.com)
Date: Thu May 03 2001 - 11:14:57 EST


Looks like if you remove the "inline" from the function definition this
compiles OK.

________________________________________
Michael D. Black Principal Engineer
mblack@csihq.com 321-676-2923,x203
http://www.csihq.com Computer Science Innovations
http://www.csihq.com/~mike My home page
FAX 321-676-2355
----- Original Message -----
From: "Christian Iseli" <chris@ludwig-alpha.unil.ch>
To: <linux-kernel@vger.kernel.org>
Sent: Wednesday, May 02, 2001 12:13 PM
Subject: Linux 2.4.4-ac3, asm problem in asm-i386/rwsem.h using gcc 3.0 CVS

Hi folks,

I currently fail to compile the 2.4.4-ac3 kernel using latest GCC 3.0 from
CVS:
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
 -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
 -mpreferred-stack-boundary=2 -march=i686 -DEXPORT_SYMTAB -c sys.c
sys.c: In function `sys_gethostname':
/usr/src/linux/include/asm/rwsem.h:152:
 inconsistent operand constraints in an `asm'

Here is the code exerpt:
/*
 * unlock after reading
 */
static inline void __up_read(struct rw_semaphore *sem)
{
        __s32 tmp = -RWSEM_ACTIVE_READ_BIAS;
        __asm__ __volatile__(
                "# beginning __up_read\n\t"
LOCK_PREFIX " xadd %%edx,(%%eax)\n\t" /* subtracts 1, returns the
old value */
                " js 2f\n\t" /* jump if the lock is being waited
upon */
                "1:\n\t"
                ".section .text.lock,\"ax\"\n"
                "2:\n\t"
                " decw %%dx\n\t" /* do nothing if still outstanding
active readers */
                " jnz 1b\n\t"
                " pushl %%ecx\n\t"
                " call rwsem_wake\n\t"
                " popl %%ecx\n\t"
                " jmp 1b\n"
                ".previous\n"
                "# ending __up_read\n"
                : "+m"(sem->count), "+d"(tmp)
                : "a"(sem)
                : "memory", "cc");
}

I'm afraid I know zilch about asm constraints...
Can anybody spot the trouble (and fix it :) ?

Thanks,
Christian

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Mon May 07 2001 - 21:00:17 EST