From: "H. Peter Anvin" <hpa@zytor.com>
To: pradeep singh <p.singh.rautela@gmail.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Jesper Juhl <jesper.juhl@gmail.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Heikki Orsila <shdl@zakalwe.fi>,
Satyam Sharma <satyam.sharma@gmail.com>
Subject: Re: [PATCH] "volatile considered harmful", take 2
Date: Fri, 11 May 2007 22:32:24 -0700 [thread overview]
Message-ID: <46455168.6080904@zytor.com> (raw)
In-Reply-To: <64026d4a0705112157p75d76956g40455c7402b096d6@mail.gmail.com>
pradeep singh wrote:
>
> Sorry, for my misunderstanding but i hope Jonathan actually means
> volatile harmful only in C and not while using extended asm with gcc? Or
> does you all consider volatile while using extended asm as harmful too?
> Incidentally i came to know that using volatile in such cases may be
> still be optimized by the gcc. And the correct way is to fake a side
> effect to the gcc, which can be done using "memory" clobbering directive
> in the correct place and not "m" or "+m".
>
> Does this means to exclude volatile from extended asm also, while using
> them in kernel?
>
We were talking about "register", not "volatile".
-hpa
next prev parent reply other threads:[~2007-05-12 5:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 20:20 [PATCH] "volatile considered harmful", take 2 Jonathan Corbet
2007-05-10 20:38 ` jimmy bahuleyan
2007-05-10 21:44 ` Satyam Sharma
2007-05-11 12:21 ` Johannes Stezenbach
2007-05-11 13:52 ` jimmy bahuleyan
2007-05-11 14:21 ` Satyam Sharma
2007-05-10 21:34 ` Jan Engelhardt
2007-05-10 21:45 ` H. Peter Anvin
2007-05-11 21:33 ` Jan Engelhardt
2007-05-11 21:47 ` H. Peter Anvin
[not found] ` <64026d4a0705112157p75d76956g40455c7402b096d6@mail.gmail.com>
2007-05-12 5:32 ` H. Peter Anvin [this message]
2007-05-11 7:41 ` Philipp Matthias Hahn
2007-05-11 8:41 ` Bernd Eckenfels
2007-05-11 11:17 ` Stefan Richter
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=46455168.6080904@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=jengelh@linux01.gwdg.de \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.singh.rautela@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=satyam.sharma@gmail.com \
--cc=shdl@zakalwe.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.