From: Jonathan Yong <10walls@gmail.com>
To: Costas Argyris <costas.argyris@gmail.com>, gcc-patches@gcc.gnu.org
Cc: Jacek Caban <jacek@codeweavers.com>
Subject: Re: Enable UTF-8 code page in driver and compiler on 64-bit mingw host [PR108865]
Date: Tue, 28 Mar 2023 08:05:21 +0000 [thread overview]
Message-ID: <f3ee6f81-2d0c-eb06-54f0-55095da7d055@gmail.com> (raw)
In-Reply-To: <CAHyHGCkfi=umcUHvYJCwFGQtUqmZM2vBYcLBksBpi5bQnOcyeQ@mail.gmail.com>
On 3/27/23 17:17, Costas Argyris wrote:
> The patch attached to this email extends the UTF-8 support of the
> driver and compiler processes to the 32-bit mingw host. Initially,
> only the 64-bit host got it.
>
> About the changes in sym-mingw32.cc:
>
> Even though the 64-bit host was building fine with the symbol being
> simply declared as a char, the 32-bit host was failing to find the
> symbol at link time because a leading underscore was being added
> to it by the compiler. The asm keyword ensures that the symbol
> always appears with that exact name, such that the linker will
> always find it.
>
> The patch also includes Jacek's flag about adding the .manifest file
> as a prerequisite for the object file (this was actually done from before
> but an earlier version of the patch was pushed so it was missed).
>
> Tested building from master for both 32 and 64-bit mingw hosts using:
>
> 1) cross-compilation from a Debian machine using configure + make
> 2) native-compilation from a Windows machine using MSYS2
>
Thanks, approved and pushed to master branch.
next prev parent reply other threads:[~2023-03-28 8:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 0:52 Costas Argyris
2023-03-07 12:01 ` Jacek Caban
2023-03-07 14:00 ` Costas Argyris
2023-03-07 14:17 ` Jacek Caban
2023-03-07 15:27 ` Costas Argyris
2023-03-08 10:52 ` Costas Argyris
2023-03-09 13:33 ` Costas Argyris
2023-03-09 15:03 ` Jonathan Yong
2023-03-27 17:17 ` Costas Argyris
2023-03-28 8:05 ` Jonathan Yong [this message]
2023-03-28 10:43 ` Costas Argyris
2023-03-28 12:03 ` Jonathan Yong
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=f3ee6f81-2d0c-eb06-54f0-55095da7d055@gmail.com \
--to=10walls@gmail.com \
--cc=costas.argyris@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jacek@codeweavers.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).