public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [patch] Reimplement GNU threads library on native Windows
Date: Sat, 29 Jun 2019 12:14:00 -0000	[thread overview]
Message-ID: <20190629121426.GQ7627@redhat.com> (raw)
In-Reply-To: <2175092.5hV0XgF4mA@polaris>

On 28/06/19 12:46 +0200, Eric Botcazou wrote:
>+/* The implementation strategy for the c++0x thread support is as follows.

s/c++0x/c++11/ please, it hasn't been 0x for eight years now :-)

I haven't reviewed the rest yet, that just jumped out at me during a
quick skim of the patch.


  parent reply	other threads:[~2019-06-29 12:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 10:50 Eric Botcazou
     [not found] ` <CAF1jjLvcXW2WitKHJYDsfL1E5LR7_WQvuY_akbe+o1WPjJO5Nw@mail.gmail.com>
2019-06-28 16:08   ` [Mingw-w64-public] Fwd: " Jacek Caban
2019-06-29  2:57     ` Liu Hao
2019-07-02  9:19       ` Eric Botcazou
2019-07-02  9:57         ` Liu Hao
2019-07-02 10:13           ` Jacek Caban
2019-07-02 10:15             ` Jacek Caban
2019-07-02 12:00               ` Jonathan Wakely
2019-07-02 12:14                 ` Liu Hao
2019-07-02 12:27                   ` Jonathan Wakely
2019-07-03 13:24                     ` Liu Hao
2019-07-29 15:05                       ` JonY
2019-07-29 15:31                         ` Liu Hao
2019-07-30  8:55                           ` Eric Botcazou
2019-06-29 12:14 ` Jonathan Wakely [this message]
2019-07-02  9:23   ` Eric Botcazou
2019-07-02  9:45     ` Jonathan Wakely
2019-07-02  9:54       ` Eric Botcazou
2019-07-02 11:56         ` Jonathan Wakely
2019-07-02 12:02           ` 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=20190629121426.GQ7627@redhat.com \
    --to=jwakely@redhat.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    /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).