From: Jonathan Yong <10walls@gmail.com>
To: i.nixman@autistici.org
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Adding a new thread model to GCC
Date: Fri, 23 Dec 2022 23:59:33 +0000 [thread overview]
Message-ID: <f454d3d7-3e70-6eb3-44d6-8213b6888a37@gmail.com> (raw)
In-Reply-To: <00af136c637f5231670c0fb6f7906d42@autistici.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 881 bytes --]
On 12/22/22 12:28, i.nixman@autistici.org wrote:
> On 2022-12-22 12:21, Jonathan Yong wrote:
>
> hello,
>
>> On 12/16/22 19:20, Eric Botcazou wrote:
>>>> The libgcc parts look reasonable to me, but I can't approve them.
>>>> Maybe Jonathan Yong can approve those parts as mingw-w64 target
>>>> maintainer, or maybe a libgcc approver can do so.
>>>
>>> OK.
>>>
>>>> The libstdc++ parts are OK for trunk. IIUC they could go in
>>>> separately, they just wouldn't be very much use without the libgcc
>>>> changes.
>>>
>>> Sure thing.
>>>
>>
>> Ping, need help to commit it?
>
> yes, it would be great if we can merge the path into gcc-13!
>
> I've tested it on gcc-12-branch and gcc-master for i686/x86_64 windows,
> with msvcrt and ucrt runtime - works as it should!
>
> Eric ^^^
>
>
>
> best!
Done, pushed to master branch. Thanks Eric.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7595 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-12-23 23:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 18:34 LIU Hao
2022-10-01 20:02 ` Bernhard Reutner-Fischer
2022-10-21 9:58 ` Jonathan Wakely
2022-10-21 10:09 ` i.nixman
2022-10-21 10:48 ` Jonathan Wakely
2022-10-21 10:55 ` i.nixman
2022-10-21 11:36 ` LIU Hao
2022-10-21 11:54 ` i.nixman
2022-10-21 12:19 ` LIU Hao
2022-10-21 12:34 ` i.nixman
2022-10-24 3:40 ` LIU Hao
2022-10-24 20:50 ` Jacek Caban
2022-10-21 11:44 ` Eric Botcazou
2022-10-21 11:55 ` i.nixman
2022-10-24 6:53 ` i.nixman
2022-10-24 8:15 ` Eric Botcazou
2022-10-24 8:20 ` i.nixman
2022-10-31 9:18 ` Eric Botcazou
2022-10-31 15:22 ` i.nixman
2022-11-01 5:22 ` i.nixman
2022-11-01 9:09 ` Eric Botcazou
2022-11-02 12:05 ` i.nixman
2022-11-02 21:27 ` Eric Botcazou
2022-11-02 21:40 ` i.nixman
2022-12-16 17:18 ` Jonathan Wakely
2022-12-16 19:20 ` Eric Botcazou
2022-12-22 12:21 ` Jonathan Yong
2022-12-22 12:28 ` i.nixman
2022-12-23 23:59 ` Jonathan Yong [this message]
2022-12-24 5:58 ` NightStrike
2022-12-24 6:27 ` i.nixman
2022-12-24 13:50 ` i.nixman
2022-12-24 15:42 ` i.nixman
2022-12-24 15:57 ` i.nixman
2022-12-24 21:22 ` i.nixman
2022-12-25 1:10 ` Jonathan Yong
2023-01-09 21:56 ` Eric Botcazou
2022-12-24 6:22 ` i.nixman
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=f454d3d7-3e70-6eb3-44d6-8213b6888a37@gmail.com \
--to=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=i.nixman@autistici.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).