From: Chuck Ebbert <76306.1226@compuserve.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@redhat.com>,
Linus Torvalds <torvalds@osdl.org>
Subject: set_bit() is broken on i386?
Date: Fri, 20 Jan 2006 19:53:14 -0500 [thread overview]
Message-ID: <200601201955_MC3-1-B649-DCF5@compuserve.com> (raw)
/*
* setbit.c -- test the Linux set_bit() function
*
* Compare the output of this program with and without the
* -finline-functions option to GCC.
*
* If they are not the same, set_bit is broken.
*
* Result on i386 with gcc 3.3.2 (Fedora Core 2):
*
* [me@d2 t]$ gcc -O2 -o setbit.ex setbit.c ; ./setbit.ex
* 00010001
* [me@d2 t]$ gcc -O2 -o setbit.ex -finline-functions setbit.c ; ./setbit.ex
* 00000001
*/
#define _GNU_SOURCE
#include <stdio.h>
#include <stdlib.h>
#define inline __attribute__((always_inline))
/*
* From 2.6.15/include/asm-i386/bitops.h -- needs a memory clobber?
*/
#define ADDR (*(volatile long *) addr)
static inline void set_bit(int nr, volatile unsigned long * addr)
{
__asm__ __volatile__( "lock ; "
"btsl %1,%0"
:"=m" (ADDR)
:"Ir" (nr));
}
unsigned long b[2];
int main(int argc, char * const argv[])
{
b[1] = 0x1;
set_bit(12 * sizeof(unsigned long), b);
printf("%08x\n", b[1]);
return 0;
}
--
Chuck
Currently reading: _Sun Of Suns_ by Karl Schroeder
next reply other threads:[~2006-01-21 0:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-21 0:53 Chuck Ebbert [this message]
2006-01-21 1:15 ` set_bit() is broken on i386? Trond Myklebust
2006-01-21 1:49 ` Andreas Schwab
2006-01-21 2:38 ` Andrew Morton
2006-01-21 19:26 ` Trond Myklebust
2006-01-21 1:32 ` Valdis.Kletnieks
2006-01-21 2:01 ` Grzegorz Kulewski
2006-01-21 1:48 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2006-01-21 1:38 Kenny Simpson
2006-01-21 1:46 Kenny Simpson
2006-01-21 2:07 Kenny Simpson
2006-01-21 7:43 Chuck Ebbert
2006-01-21 20:49 Chuck Ebbert
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=200601201955_MC3-1-B649-DCF5@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox