From: "Pali Rohár" <pali.rohar@gmail.com>
To: gcc@gcc.gnu.org
Cc: mingw-w64-public@lists.sourceforge.net, LIU Hao <lh_mouse@126.com>
Subject: Re: gcc parameter -mcrtdll= for choosing Windows C RunTime DLL library
Date: Sat, 6 May 2023 12:45:04 +0200 [thread overview]
Message-ID: <20230506104504.3pqi7mgcygvzs6db@pali> (raw)
In-Reply-To: <20230421162328.vn3wtgymnsxrbcgd@pali>
On Friday 21 April 2023 18:23:28 Pali Rohár wrote:
> On Sunday 04 December 2022 20:48:30 LIU Hao wrote:
> > 在 2022-12-04 20:16, Pali Rohár via Gcc 写道:
> > > Hello! I would like to ask gcc people, what do you think about such
> > > proposed -mcrtdll= parameter?
> > >
> > > There are lot of unofficial gcc patches which implement this -mcrtdll=
> > > parameter and this parameter is present in more gcc forks.
> > > So it looks like that this parameter is useful for more people.
> > >
> >
> > I vote +1 for this in GCC 14.
> >
> > GCC 13 (i.e. current master branch) is at stage3 so it's not an option at this moment.
> >
> >
> > --
> > Best regards,
> > LIU Hao
> >
>
> 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.
next prev parent reply other threads:[~2023-05-06 10:45 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 [this message]
2023-05-08 3:44 ` LIU Hao
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=20230506104504.3pqi7mgcygvzs6db@pali \
--to=pali.rohar@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=lh_mouse@126.com \
--cc=mingw-w64-public@lists.sourceforge.net \
/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).