From: Evgeny Karpov <Evgeny.Karpov@microsoft.com>
To: LIU Hao <lh_mouse@126.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH v2 00/13] Add aarch64-w64-mingw32 target
Date: Wed, 6 Mar 2024 14:20:39 +0000 [thread overview]
Message-ID: <VI1PR83MB043174C068F4CFEE519CC6DCF8212@VI1PR83MB0431.EURPRD83.prod.outlook.com> (raw)
In-Reply-To: <3c1efc86-ff09-47bd-9eda-8e6945149940@126.com>
Wednesday, March 6, 2024
LIU Hao wrote:
> May I suggest you keep the mcf thread model for aarch-w64-mingw32? I
> requested Martin Storsjö to test it on a physical Windows 11 on ARM machine
> with Clang and all tests passed. I think it should work once the GCC support is
> complete.
>
>
> --
> Best regards,
> LIU Hao
The MCF thread model will be added to the aarch64-w64-mingw32 target
in the next patch series. Most probably, this will occur when the
mingw unit tests are integrated into the aarch64-w64-mingw32 target.
Regards,
Evgeny
next prev parent reply other threads:[~2024-03-06 14:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 8:40 LIU Hao
2024-03-06 14:20 ` Evgeny Karpov [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-04 17:24 Evgeny Karpov
2024-03-04 17:55 ` Evgeny Karpov
2024-03-04 19:25 ` Evgeny Karpov
2024-03-07 20:47 ` Evgeny Karpov
2024-03-18 13:33 ` Christophe Lyon
2024-03-18 22:10 ` Evgeny Karpov
2024-03-18 22:58 ` Fangrui Song
2024-03-18 23:22 ` Andrew Pinski
2024-03-19 7:50 ` Martin Storsjö
2024-03-18 21:05 ` Radek Barton
2024-03-20 11:50 ` Radek Barton
2024-03-20 19:37 ` NightStrike
2024-04-10 18:40 ` Richard Sandiford
2024-04-11 14:14 ` Evgeny Karpov
2024-04-11 14:34 ` Richard Sandiford
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=VI1PR83MB043174C068F4CFEE519CC6DCF8212@VI1PR83MB0431.EURPRD83.prod.outlook.com \
--to=evgeny.karpov@microsoft.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=lh_mouse@126.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).