From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] const
Date: Fri, 9 Dec 2005 09:42:48 -0800 [thread overview]
Message-ID: <3e1162e60512090942w50850e9cv9a8d8d4870a6e81c@mail.gmail.com> (raw)
In-Reply-To: <676c3c4f0512090859n72ec5bd1rfa7742b43faf526b@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
> It is a matter of faith, and usually misplaced at that, since volatile
> isn't usually defined to place any constraints on the order in which
> operations become visible to other processors. Certainly not in the C, C++,
> or POSIX standards, although some platform ABIs do specify this to some
> degree.
>
> Both POSIX and C++ are trying to deal with this, but it's an uphill battle
> since processors differ widely on the sorts of constraints that they can
> support efficiently.
>
> In the meantime, people sprinkle volatile around and pray. All the world's
> an x86, right?
>
I think I'd be happier with new compiler pragmas in this case than a
keyword. Then at least I KNOW that it can be ignored and will be optionally
supported by compilers on a per-case basis.
But then again, that's also true for "inline" in C++. It's just a
suggestion, one that can be ignored. The compiler can also inline stuff I
didn't ask it to. [C99 has inline now too doesn't it?]
[-- Attachment #2: Type: text/html, Size: 1230 bytes --]
next prev parent reply other threads:[~2005-12-09 17:42 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 10:34 Steve Simon
2005-12-07 12:17 ` Russ Cox
2005-12-07 13:01 ` erik quanstrom
[not found] ` <000401c5fb32$64502e00$14aaa8c0@utelsystems.local>
2005-12-07 14:10 ` "Nils O. Selåsdal"
2005-12-07 15:05 ` Steve Simon
2005-12-07 15:30 ` Lucio De Re
2005-12-07 15:53 ` C H Forsyth
[not found] ` <1E68F99F-78D7-4321-BE56-7D0319212596@telus.net>
2005-12-07 16:11 ` "Nils O. Selåsdal"
2005-12-07 17:27 ` Paul Lalonde
2005-12-07 16:23 ` jmk
2005-12-07 17:28 ` Skip Tavakkolian
2005-12-07 18:51 ` Joel Salomon
2005-12-07 18:58 ` Charles Forsyth
2005-12-07 19:30 ` Joel Salomon
2005-12-07 19:36 ` Brantley Coile
2005-12-07 19:51 ` rog
2005-12-07 21:07 ` Charles Forsyth
2005-12-07 21:18 ` Bruce Ellis
2005-12-07 21:22 ` Paul Lalonde
2005-12-07 22:04 ` Rob Pike
2005-12-07 22:44 ` Micah Stetson
2005-12-07 22:44 ` Micah Stetson
2005-12-07 22:46 ` Brantley Coile
2005-12-07 20:33 ` Skip Tavakkolian
2005-12-08 7:39 ` geoff
2005-12-08 7:53 ` Lucio De Re
2005-12-08 7:54 ` geoff
2005-12-08 10:23 ` Bruce Ellis
2005-12-08 15:58 ` Brantley Coile
2005-12-09 1:44 ` geoff
2005-12-09 2:04 ` Russ Cox
2005-12-09 2:19 ` geoff
2005-12-09 9:54 ` Charles Forsyth
2005-12-09 16:25 ` David Leimbach
2005-12-09 16:59 ` Richard Bilson
2005-12-09 17:42 ` David Leimbach [this message]
2005-12-09 19:17 ` Richard Bilson
2005-12-09 17:01 ` Ronald G Minnich
2005-12-09 17:39 ` Russ Cox
2005-12-09 17:40 ` [9fans] PCICIA Modem TamTam
2005-12-09 18:59 ` Sascha Retzki
2005-12-12 15:07 ` Paweł Lasek
2005-12-26 9:00 ` Martin C. Atkins
2005-12-26 14:19 ` Paweł Lasek
2005-12-09 19:37 ` [9fans] Re: const Nikita Danilov
2005-12-09 20:30 ` Russ Cox
2005-12-09 20:37 ` Ronald G Minnich
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=3e1162e60512090942w50850e9cv9a8d8d4870a6e81c@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).