public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Yong <10walls@gmail.com>
To: "Pali Rohár" <pali@kernel.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2] Add MinGW option -mcrtdll= for choosing C RunTime DLL library
Date: Fri, 16 Jun 2023 13:18:09 +0000	[thread overview]
Message-ID: <6a46e368-87fe-c3e1-f468-cf6d983c1d53@gmail.com> (raw)
In-Reply-To: <20230614160917.13046-1-pali@kernel.org>

On 6/14/23 16:09, Pali Rohár wrote:
> It adjust preprocess, compile and link flags, which allows to change
> default -lmsvcrt library by another provided by MinGW runtime.
> 
> gcc/
>       * config/i386/mingw-w64.h (CPP_SPEC): Adjust for -mcrtdll=.
>       (REAL_LIBGCC_SPEC): New define.
>       * config/i386/mingw.opt: Add mcrtdll=
>       * config/i386/mingw32.h (CPP_SPEC): Adjust for -mcrtdll=.
>       (REAL_LIBGCC_SPEC): Adjust for -mcrtdll=.
>       (STARTFILE_SPEC): Adjust for -mcrtdll=.
>       * doc/invoke.texi: Add mcrtdll= documentation.
> ---
> Changes in v2:
> * Fixed doc/invoke.texi documentation
> ---
>   gcc/config/i386/mingw-w64.h | 22 +++++++++++++++++++++-
>   gcc/config/i386/mingw.opt   |  4 ++++
>   gcc/config/i386/mingw32.h   | 28 ++++++++++++++++++++++++----
>   gcc/doc/invoke.texi         | 24 +++++++++++++++++++++++-
>   4 files changed, 72 insertions(+), 6 deletions(-)
> 

Thanks, pushed to master branch.



      reply	other threads:[~2023-06-16 13:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 10:14 [PATCH] " Pali Rohár
2023-06-11 23:08 ` Jonathan Yong
2023-06-12  1:26   ` LIU Hao
2023-06-12 23:13     ` Jonathan Yong
2023-06-13  6:29       ` Pali Rohár
2023-06-13  8:40         ` LIU Hao
2023-06-14 16:09 ` [PATCH v2] " Pali Rohár
2023-06-16 13:18   ` Jonathan Yong [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=6a46e368-87fe-c3e1-f468-cf6d983c1d53@gmail.com \
    --to=10walls@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=pali@kernel.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).