On 3/28/23 10:43, Costas Argyris wrote:
I forgot to update the relevant comments with the previous patch.
This is a comment-only patch that brings them up-to-date.
Done, thanks.
I forgot to update the relevant comments with the previous patch.
This is a comment-only patch that brings them up-to-date.
On Tue, 28 Mar 2023 at 09:05, Jonathan Yong <10wa...@gmail.com> wrote:
> On 3/27/23 17:17, Costas Argyris wrote:
> > The patch attached to this email extends the UTF-8 supp
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 th
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,
On 3/9/23 13:33, Costas Argyris wrote:
Pinging the list and mingw maintainer.
Analysis and pre-approval here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
Thanks, pushed to master branch.
Pinging the list and mingw maintainer.
Analysis and pre-approval here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
On Wed, 8 Mar 2023 at 10:52, Costas Argyris
wrote:
> Added .manifest file to the make rule for utf8rc-mingw32.o, latest patch
> attached.
>
> On Tue, 7 Mar 2023 at 15:27,
Added .manifest file to the make rule for utf8rc-mingw32.o, latest patch
attached.
On Tue, 7 Mar 2023 at 15:27, Costas Argyris
wrote:
> Hi Jacek,
>
> "but I think it should work just fine if you didn't explicitly limit the
> patch to x86_64."
>
> I would think so too.
>
> Actually, even cygwin m
Hi Jacek,
"but I think it should work just fine if you didn't explicitly limit the
patch to x86_64."
I would think so too.
Actually, even cygwin might benefit from this, assuming it has the same
problem, which I don't know if it's the case.
But I'm not experienced with that so I would like to e
Hi Costas,
On 3/7/23 15:00, Costas Argyris wrote:
Hi Jacek,
"Is there a reason to make it specific to x86_64? It seems to me that
all mingw hosts could use it."
Are you referring to the 32-bit host? My concern here is that this
functionality (embedding the UTF-8
manifest file into the ex
Hi Jacek,
"Is there a reason to make it specific to x86_64? It seems to me that all
mingw hosts could use it."
Are you referring to the 32-bit host?My concern here is that this
functionality (embedding the UTF-8
manifest file into the executable) is only truly supported in recent
versions of
Hi Costas,
On 3/7/23 01:52, Costas Argyris via Gcc-patches wrote:
This is a proposal for addressing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
by integrating the UTF-8 manifest file into gcc's build process for the
64-bit mingw host.
Is there a reason to make it specific to x86_64?
Hi
This is a proposal for addressing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
by integrating the UTF-8 manifest file into gcc's build process for the
64-bit mingw host.
The analysis and discussion leading up to the latest patch are written in
the bug report.
The patch attached in th
12 matches
Mail list logo
