From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 8c - is this leagal?
Date: Wed, 21 Nov 2012 14:09:40 +0000 [thread overview]
Message-ID: <CAOw7k5j8xQgRjPcJKiCozYkOaCVvr7b7eZ6wyMSzi5ec02Gjyw@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5i8i+s+tCc4RDSFZzviPGShTA8NX8mBZ4WRmUtz87ewLg@mail.gmail.com>
By which I meant that yes, it's legal ANSI C code to combine them. The
strange way the compiler implements volatile references probably led
to that odd diagnostic.
As I said, I'd try nopping the volatile.
On 21 November 2012 13:30, Charles Forsyth <charles.forsyth@gmail.com> wrote:
> static is scope, volatile has dynamic effects, very dynamic.
next prev parent reply other threads:[~2012-11-21 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 13:21 Steve Simon
2012-11-21 13:30 ` Charles Forsyth
2012-11-21 13:31 ` Charles Forsyth
2012-11-21 14:09 ` Charles Forsyth [this message]
2012-11-21 15:51 ` Steve Simon
2012-11-21 15:53 ` erik quanstrom
2012-11-21 13:30 ` Bence Fábián
2012-11-21 14:56 ` Dan Cross
2012-11-21 15:03 ` Bence Fábián
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=CAOw7k5j8xQgRjPcJKiCozYkOaCVvr7b7eZ6wyMSzi5ec02Gjyw@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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).