Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@redhat.com>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
	ralf@linux-mips.org, linux-mips@linux-mips.org,
	macro@linux-mips.org
Subject: Re: [PATCH] I/O helpers rework
Date: Thu, 13 Jan 2005 21:48:36 +0000	[thread overview]
Message-ID: <87k6qh2e6j.fsf@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0501131824350.21179@perivale.mips.com> (Maciej W. Rozycki's message of "Thu, 13 Jan 2005 18:25:57 +0000 (GMT)")

"Maciej W. Rozycki" <macro@mips.com> 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

  reply	other threads:[~2005-01-13 21:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 21:13 [PATCH] I/O helpers rework Maciej W. Rozycki
2005-01-06 15:45 ` Atsushi Nemoto
2005-01-10 15:28   ` Maciej W. Rozycki
2005-01-10 17:21     ` Atsushi Nemoto
2005-01-10 18:11       ` Maciej W. Rozycki
2005-01-11  0:53         ` Atsushi Nemoto
2005-01-13 18:12         ` Richard Sandiford
2005-01-13 18:25           ` Maciej W. Rozycki
2005-01-13 21:48             ` Richard Sandiford [this message]
2005-01-14  1:52               ` Atsushi Nemoto
2005-01-14 11:05                 ` Richard Sandiford
2005-01-14 19:57               ` Maciej W. Rozycki
2005-01-21 16:50   ` Atsushi Nemoto
2005-01-22  2:51     ` Maciej W. Rozycki
2005-01-25  1:09       ` Atsushi Nemoto
2005-02-17  1:34       ` Ralf Baechle
2005-02-18 19:44         ` Maciej W. Rozycki
2005-01-06 16:33 ` Herbert Valerio Riedel
2005-01-10 13:05   ` Maciej W. Rozycki
2005-01-10 14:46     ` Herbert Valerio Riedel
2005-01-10 14:49       ` Herbert Valerio Riedel
2005-01-14 20:07         ` Maciej W. Rozycki
2005-01-13 22:18 ` Manish Lachwani

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k6qh2e6j.fsf@redhat.com \
    --to=rsandifo@redhat.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=macro@mips.com \
    --cc=ralf@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox