9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Joel C. Salomon" <joelcsalomon@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] NUMA
Date: Sun, 17 Jul 2011 11:05:41 -0400	[thread overview]
Message-ID: <4E22FA45.7060006@gmail.com> (raw)
In-Reply-To: <20110717070120.GA539@polynum.com>

On 07/17/2011 03:01 AM, tlaronde@polynum.com wrote:
> On Sat, Jul 16, 2011 at 11:39:50PM -0400, Joel C. Salomon wrote:
>> On 07/16/2011 04:02 AM, tlaronde@polynum.com wrote:
>>>                I wonder what minimum set of keywords could be added,
>>> say, to C, so that the situation can be greatly improved without the
>>> burden being greatly increased. [non-predicative routines being, from
>>> a parallel point of view, atomic]
>>
>> Have a look at what the C1x standard is proposing wrt atomics.
>
> Thanks for the tip!
>
> BTW, if I understand correctly the purpose of the next C standard, I
> guess there is no urge for kencc to support C99
> since it is already a transitory only partially supported standard.

The only place in which that's relevant is that C1x creates language
subsets and some of the new language features are optional.  (I.e., if
your compiler doesn't implement feature x, predefine this macro X and
you can still call your compiler conforming.)  The only C99 feature
listed as optional is VLAs.

BTW, C1x standardizes part of kencc's nested-anonymous-struct feature.

--Joel



  reply	other threads:[~2011-07-17 15:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-15 15:15 tlaronde
2011-07-15 20:21 ` tlaronde
2011-07-15 20:47   ` ron minnich
2011-07-15 22:59     ` Charles Forsyth
2011-07-16  8:02     ` tlaronde
2011-07-16 16:27       ` erik quanstrom
2011-07-16 18:06         ` tlaronde
2011-07-16 19:29           ` Ethan Grammatikidis
2011-07-16 19:54           ` erik quanstrom
2011-07-16 20:56             ` dexen deVries
2011-07-16 22:10               ` Charles Forsyth
2011-07-17  1:44                 ` erik quanstrom
2011-07-17  7:38                   ` tlaronde
2011-07-17  8:44                     ` Bakul Shah
2011-07-17 10:02                       ` tlaronde
2011-07-17 12:04                         ` dexen deVries
2011-07-17 15:24                       ` erik quanstrom
2011-07-17 15:28                         ` ron minnich
     [not found]                         ` <CAP6exYL2DJXbKfPZ8+D5uL=fRWKEyr8vY2OVc4NTO3wsFo=Unw@mail.gmail.c>
2011-07-17 15:32                           ` erik quanstrom
2011-07-17 17:16                         ` Bakul Shah
2011-07-17 17:21                           ` erik quanstrom
2011-07-17 15:51                     ` erik quanstrom
2011-07-17 16:12                       ` dexen deVries
2011-07-17 16:37                       ` tlaronde
2011-07-17 10:08               ` Ethan Grammatikidis
2011-07-17 14:50                 ` erik quanstrom
2011-07-17 17:01                   ` Ethan Grammatikidis
2011-07-17  3:39       ` Joel C. Salomon
2011-07-17  7:01         ` tlaronde
2011-07-17 15:05           ` Joel C. Salomon [this message]
2011-07-17 15:26           ` erik quanstrom
2011-07-17 15:52             ` ComeauAt9Fans@gmail.com

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=4E22FA45.7060006@gmail.com \
    --to=joelcsalomon@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).