Date: Thu, 21 Mar 2002 09:31:30 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: obrien@FreeBSD.ORG Cc: Warner Losh <imp@harmony.village.org>, alpha@FreeBSD.ORG Subject: Re: Expected compiler error on GENERIC? Message-ID: <15513.61122.201509.896981@grasshopper.cs.duke.edu> In-Reply-To: <20020320154150.A90810@dragon.nuxi.com> References: <15513.4041.407099.858575@grasshopper.cs.duke.edu> <20020320.153148.103780390.imp@village.org> <200203202313.g2KND6L12819@harmony.village.org> <20020320154150.A90810@dragon.nuxi.com>
index | next in thread | previous in thread | raw e-mail
David O'Brien writes:
> On Wed, Mar 20, 2002 at 04:13:06PM -0700, Warner Losh wrote:
> > The line in question is
> > if (!badaddr((void *)&t2_csr[1]->tlbbr, sizeof(long))) {
> > but I don't know what the type of tlbbr is, but it is either volatile
> > or const for some reason...
>
> `tlbbr' is u_long.
> `t2_csr' is "volatile", and is the source of the warning.
Please: what's the proper way to cast away the volatile & shut the
f*ing compiler up?
FWIW, the code is checking for hardware which the docs state may be
present, but which nobody has encountered in the wild & which FreeBSD
is (currently) unprepared to deal with. If anybody complains that
FreeBSD doesn't see the second PCI hose on a sable or lynx, that
"Found EXT_IO!!!!" printf in their dmesg will remind me of what's
going on. As a last resort, the check could be removed, but I'd
prefer to leave it there.
Drew
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15513.61122.201509.896981>