public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@inria.fr>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "Erotavlas_turbo@libero.it" <Erotavlas_turbo@libero.it>,
	    gcc-help@gcc.gnu.org
Subject: Re: GCC: C0x11 threading support
Date: Fri, 25 Nov 2011 15:19:00 -0000	[thread overview]
Message-ID: <alpine.DEB.2.02.1111251120310.2513@laptop-mg.saclay.inria.fr> (raw)
In-Reply-To: <CAH6eHdTN8dg+AjVMePRF8KBbZ6AY_AiZujffkAPHaAjhze5fmQ@mail.gmail.com>

On Fri, 25 Nov 2011, Jonathan Wakely wrote:

> On 25 November 2011 08:59, Erotavlas_turbo@libero.it wrote:
>> Hi,
>>
>> I have read that the threading programming proposed in new C++ standard
>> (C0x11)
>
> (It was informally called C++0x but is now published and often
> referred to as C++11, but calling it C++0x11 makes no sense.)
>
>> is supported by GCC but only a small subset of features are available.
>> So for the moment is better to use the boost thread library (that should be the
>> same adopted by new standard, correct me if I'm wrong) or the complete support
>> by GCC is not so far?
>
> Since you suggest Boost as an alternative I assume you are only
> talking about the new library classes (since that's all Boost
> provides).  The library features are almost complete:
> http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.200x
>
> There is more work to be done for the core language features:
> http://gcc.gnu.org/projects/cxx0x.html
> http://gcc.gnu.org/wiki/Atomic/
> http://gcc.gnu.org/wiki/Atomic/GCCMM

Those don't seem to mention that the branch was recently merged into 
trunk. That doesn't make the support complete though.

-- 
Marc Glisse

  parent reply	other threads:[~2011-11-25 10:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25 10:24 Erotavlas_turbo
2011-11-25 12:26 ` Jonathan Wakely
2011-11-25 13:11   ` Jonathan Wakely
2011-11-25 15:19   ` Marc Glisse [this message]
2011-11-25 21:16     ` Jonathan Wakely
2011-11-26 14:31       ` Andrew MacLeod
2011-11-29 11:13 Erotavlas_turbo
2011-11-29 11:19 ` Jonathan Wakely
2011-11-29 13:30 Erotavlas_turbo
2011-11-29 15:36 ` Jonathan Wakely
2011-11-29 20:21 Erotavlas_turbo
2011-11-29 22:48 ` Jonathan Wakely

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=alpine.DEB.2.02.1111251120310.2513@laptop-mg.saclay.inria.fr \
    --to=marc.glisse@inria.fr \
    --cc=Erotavlas_turbo@libero.it \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).