public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Qiye Tan <qiye.c.tan@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: The problem(difference) in the gnu website about C++11 support in a specific version of GCC
Date: Mon, 13 Apr 2020 15:02:06 +0100	[thread overview]
Message-ID: <CAH6eHdTkD=bNXcxBcuS-tYE4HTBBoNaejMGyezbxwrgg5Bh9hA@mail.gmail.com> (raw)
In-Reply-To: <CAAvJhirY9qQGM4h-PEFqyQjSZManRpakfF1YCqjD5Nb4SSroDg@mail.gmail.com>

On Mon, 13 Apr 2020 at 06:22, Qiye Tan via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> Dear GCC Helper:
>
>
>
> I have found that in website:
> https://gcc.gnu.org/projects/cxx-status.html#cxx11, the Table Concurrency
> shows that GCC 4.3 support the proposal N2660, however, when I went to GCC
> 4.3 c++0x status website (https://gcc.gnu.org/gcc-4.3/cxx0x_status.html)
> for detail information, I found that it shows that GCC 4.3 doesn’t support
> proposal N2660.

It's likely the gcc-4.3 docs were not updated at the time, and so are incorrect.

> What’s more, I don’t know why my gcc doesn’t have the
> predefine MACRO “__cpp_threadsafe_static_init”, it even doesn’t have the
> MACRO “__cpp_rtti”.

GCC 4.3.6 was released in 2011.

The initial proposal for the idea of standardized macros was published in 2012:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2012/n3435.htm
The first "__cpp_xxx" macros were proposed in 2013:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3694.htm
But the __cpp_rtti macro wasn't proposed until much later:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4200.htm
And the __cpp_threadsafe_static_init macro even later:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0096r5.html

It's completely unsurprising that a compiler released in 2011 doesn't
implement a feature invented several years later.


> So, can you tell me that whether threadsafe_static_init
> is supported in GCC 4.3? Thank you so much!

The -fno-threadsafe-statics option is documented in the GCC 4.3
manual, so yes, it's supported.

      reply	other threads:[~2020-04-13 14:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13  5:20 Qiye Tan
2020-04-13 14:02 ` Jonathan Wakely [this message]

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='CAH6eHdTkD=bNXcxBcuS-tYE4HTBBoNaejMGyezbxwrgg5Bh9hA@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=qiye.c.tan@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).