From: LIU Hao <lh_mouse@126.com>
To: "Pali Rohár" <pali.rohar@gmail.com>, gcc@gcc.gnu.org
Cc: mingw-w64-public@lists.sourceforge.net
Subject: Re: gcc parameter -mcrtdll= for choosing Windows C RunTime DLL library
Date: Mon, 8 May 2023 11:44:17 +0800 [thread overview]
Message-ID: <6b4a966a-3cb0-b4e8-d8c9-2b6a5b8df3b3@126.com> (raw)
In-Reply-To: <20230506104504.3pqi7mgcygvzs6db@pali>
[-- Attachment #1.1: Type: text/plain, Size: 777 bytes --]
在 2023/5/6 18:45, Pali Rohár 写道:
>> Hello! If I'm looking correctly, gcc 13 was already branched. So what
>> revisiting this -mcrtdll= parameter now?
>
> Hello! I would like to remind this -mcrtdll= support for gcc.
As said before, the idea sounds good. But in order for your patch to be checked in, you need to
1) Sign off your commit.
2) Append ChangeLog entries to the commit message. You may take other commits
as references. They are required for all directories with a ChangeLog file,
and will be parsed by server-side Git hook scripts.
3) Send this patch to gcc-patches@gcc.gnu.org with a CC to Jonathan Yong
<10walls@gmail.com>, who is the only maintainer on GCC for mingw-w64 port.
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-05-08 3:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 12:53 Pali Rohár
2022-11-20 13:36 ` [Mingw-w64-public] " LIU Hao
2022-11-20 15:06 ` Pali Rohár
2022-11-21 5:21 ` LIU Hao
2022-11-26 19:09 ` Pali Rohár
2022-11-27 1:06 ` sotrdg sotrdg
2022-11-20 14:45 ` Eli Zaretskii
2022-11-20 15:04 ` Pali Rohár
2022-11-20 15:23 ` Eli Zaretskii
2022-11-20 15:44 ` Pali Rohár
2022-11-20 15:58 ` Eli Zaretskii
2022-11-20 16:19 ` [Mingw-w64-public] " ralph engels
2022-11-20 16:20 ` Matthew Brett
2022-11-20 21:22 ` Martin Storsjö
2022-12-04 12:16 ` Pali Rohár
2022-12-04 12:48 ` LIU Hao
2023-04-21 16:23 ` Pali Rohár
2023-05-06 10:45 ` Pali Rohár
2023-05-08 3:44 ` LIU Hao [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=6b4a966a-3cb0-b4e8-d8c9-2b6a5b8df3b3@126.com \
--to=lh_mouse@126.com \
--cc=gcc@gcc.gnu.org \
--cc=mingw-w64-public@lists.sourceforge.net \
--cc=pali.rohar@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).