From owner-freebsd-alpha Thu Mar 21 6:32:24 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id AFFC837B41A; Thu, 21 Mar 2002 06:32:07 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA02987; Thu, 21 Mar 2002 09:32:00 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g2LEVUf08259; Thu, 21 Mar 2002 09:31:30 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15513.61122.201509.896981@grasshopper.cs.duke.edu> Date: Thu, 21 Mar 2002 09:31:30 -0500 (EST) To: obrien@FreeBSD.ORG Cc: Warner Losh , alpha@FreeBSD.ORG Subject: Re: Expected compiler error on GENERIC? 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> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 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