Date: Wed, 27 Jan 1999 18:16:12 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: current@FreeBSD.ORG Subject: Changing bzero, bcopy, memset, memcpy, etc... prototypes Message-ID: <199901280216.SAA90783@apollo.backplane.com> References: <Pine.BSF.4.05.9901272113380.81323-100000@bright.fx.genx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
I would like to propose changing the prototype for the kernel memory
zeroing and copying routines.
Basically, the problem is that a whole hellofalot of drivers run
bzero and bcopy on volatile memory. The only way to remove the
warnings is to volatilize bzero and bcopy.
The compiler will, I believe, upgrade a pointer to a non-volatile
(aka char *) to a pointer to a volatile (aka volatile char *) without
issuing any warnings.
This change should be fully backwards compatible.
So I propose changing
FROM
void bzero __P((void *buf, size_t len));
void bcopy __P((const void *from, void *to, size_t len));
TO
void bzero __P((volatile void *buf, size_t len));
void bcopy __P((volatile const void *from, volatile void *to, size_t len));
Comments?
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901280216.SAA90783>
