diff options
| author | peter <peter@FreeBSD.org> | 1999-05-09 23:30:01 +0000 |
|---|---|---|
| committer | peter <peter@FreeBSD.org> | 1999-05-09 23:30:01 +0000 |
| commit | 593dd5803d65c079b5298621bfe839a237b1b66e (patch) | |
| tree | b1106684662305ca2b644eaa7bba0dc67a207248 /sys/i386/include/cpufunc.h | |
| parent | 1b1bfd57f3ccf4c0eb8d280acf3b03eeeea1e6af (diff) | |
| download | FreeBSD-src-593dd5803d65c079b5298621bfe839a237b1b66e.zip FreeBSD-src-593dd5803d65c079b5298621bfe839a237b1b66e.tar.gz | |
loadandclear() uses an atomic instruction (even on SMP, where it's an
implicitly LOCK'ed instruction), so there shouldn't be any harm in making
it volatile pointer compatable for one of the users of it. It seems to
generate the same code regardless.
Diffstat (limited to 'sys/i386/include/cpufunc.h')
| -rw-r--r-- | sys/i386/include/cpufunc.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/sys/i386/include/cpufunc.h b/sys/i386/include/cpufunc.h index c1f9f17..2733e72 100644 --- a/sys/i386/include/cpufunc.h +++ b/sys/i386/include/cpufunc.h @@ -30,7 +30,7 @@ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF * SUCH DAMAGE. * - * $Id: cpufunc.h,v 1.85 1999/01/09 13:00:27 bde Exp $ + * $Id: cpufunc.h,v 1.86 1999/04/28 01:03:58 luoqi Exp $ */ /* @@ -289,7 +289,7 @@ inw(u_int port) } static __inline u_int -loadandclear(u_int *addr) +loadandclear(volatile u_int *addr) { u_int result; |
