From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 13 Jan 2005 21:48:46 +0000 (GMT) Received: from mx1.redhat.com ([IPv6:::ffff:66.187.233.31]:30080 "EHLO mx1.redhat.com") by linux-mips.org with ESMTP id ; Thu, 13 Jan 2005 21:48:40 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j0DLmc2V023438; Thu, 13 Jan 2005 16:48:38 -0500 Received: from localhost (mail@vpn50-41.rdu.redhat.com [172.16.50.41]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j0DLmbr07703; Thu, 13 Jan 2005 16:48:37 -0500 Received: from rsandifo by localhost with local (Exim 3.35 #1) id 1CpCpY-00007m-00; Thu, 13 Jan 2005 21:48:36 +0000 To: "Maciej W. Rozycki" Cc: Atsushi Nemoto , ralf@linux-mips.org, linux-mips@linux-mips.org, macro@linux-mips.org Subject: Re: [PATCH] I/O helpers rework References: <20050107.004521.74752947.anemo@mba.ocn.ne.jp> <20050111.022138.25909508.anemo@mba.ocn.ne.jp> <874qhltcyv.fsf@redhat.com> From: Richard Sandiford Date: Thu, 13 Jan 2005 21:48:36 +0000 In-Reply-To: (Maciej W. Rozycki's message of "Thu, 13 Jan 2005 18:25:57 +0000 (GMT)") Message-ID: <87k6qh2e6j.fsf@redhat.com> User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 6906 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: rsandifo@redhat.com Precedence: bulk X-list: linux-mips "Maciej W. Rozycki" writes: > On Thu, 13 Jan 2005, Richard Sandiford wrote: > >> >> Well, maybe the 'volatile' have no sense, but some archs (including >> >> i386, of course :-)) and some drivers use it. Adding the 'volatile' >> >> will remove some compiler warnings. >> > >> > As will removing "volatile" from broken ports. >> >> There's nothing wrong with "volatile void *". > > So what's the volatile value you can get by dereferencing such a pointer? You can't dereference it, obviously, just like you can't deference a normal "void *". But you can assign it to any "volatile T *" without an explicit cast. I assumed that's what was happening in this case? Richard