Date: Fri, 22 Mar 2002 08:49:30 +0000 (GMT) From: Doug Rabson <dfr@nlsystems.com> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: <obrien@FreeBSD.ORG>, Warner Losh <imp@harmony.village.org>, <alpha@FreeBSD.ORG> Subject: Re: Expected compiler error on GENERIC? Message-ID: <20020322084903.F99274-100000@salmon.nlsystems.com> In-Reply-To: <15513.61122.201509.896981@grasshopper.cs.duke.edu>
index | next in thread | previous in thread | raw e-mail
On Thu, 21 Mar 2002, Andrew Gallatin wrote:
>
> 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.
Perhaps badaddr should take a volatile pointer argument?
--
Doug Rabson Mail: dfr@nlsystems.com
Phone: +44 20 8348 6160
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020322084903.F99274-100000>