public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: LIU Hao <lh_mouse@126.com>
To: Arthur Cohen <arthur.cohen@embecosm.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [PATCH] Fix rust on *-w64-mingw32
Date: Fri, 26 Apr 2024 19:14:53 +0800	[thread overview]
Message-ID: <125e70f6-9cc5-4409-98f5-54439606c22f@126.com> (raw)
In-Reply-To: <76cc558c-49bf-40f1-b28c-a62584f62e00@embecosm.com>


[-- Attachment #1.1: Type: text/plain, Size: 983 bytes --]

在 2024-04-26 18:47, Arthur Cohen 写道:
> Hello,
> 
> Thanks a lot for the patch :)
> 
> I agree with Jakub that we should be using the GNU coding style in our call to std::replace - this 
> is what we try to enforce in the rest of the Rust frontend.

Please feel welcome to rewrite the patch as necessary. It was sent only for illustration about the 
build issues.


> could you change it to something simpler like simply ignoring the return value of `mkdir`? since 
> this is what we are already doing (and we should improve error handling here... but one battle at a 
> time).

I don't know why there is such a function. It might be better to just replace it with direct calls 
to `mkdir()`.


> Have you run the testsuite on *-w64-mingw32? I'm wondering if commenting out the `register_callback` 
> function causes any issues there?

No. I only bootstrapped GCC itself with Rust enabled. I know nothing about Rust.



-- 
Best regards,
LIU Hao


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2024-04-26 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 11:16 LIU Hao
2024-04-25 11:19 ` Jakub Jelinek
2024-04-26 10:47 ` Arthur Cohen
2024-04-26 11:14   ` LIU Hao [this message]
2024-04-27 15:57     ` 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=125e70f6-9cc5-4409-98f5-54439606c22f@126.com \
    --to=lh_mouse@126.com \
    --cc=arthur.cohen@embecosm.com \
    --cc=gcc@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).