[Bug c/108678] New: Windows on ARM64 platform target aarch64-w64-mingw32

[Bug c/108678] New: Windows on ARM64 platform target aarch64-w64-mingw32

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

            Bug ID: 108678
           Summary: Windows on ARM64 platform target aarch64-w64-mingw32
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: brechtsanders at users dot sourceforge.net
  Target Milestone: ---

Are there plans to support Windows (using MinGW-w64) on ARM64?

The triplet for this platform should be: aarch64-w64-mingw32

I'm trying to build natively on a Windows on ARM device (bootstrapping from
LLVM/CLang).

Since binutils 2.40 there some support for aarch64 COFF/PE format, and I
already built a working binutils with the following supported targets:

ld --help|sed -n "s/^.*supported targets: //p"
pe-x86-64 pei-x86-64 pe-bigobj-x86-64 elf64-x86-64 pe-i386 pei-i386 elf32-i386
elf32-iamcu pdb elf64-little elf64-big elf32-little elf32-big pe-bigobj-i386
pe-aarch64-little pei-aarch64-little srec symbolsrec verilog tekhex binary ihex
plugin

So it looks like pe-aarch64-little and pei-aarch64-little are listed.

I'm don't know if a pe-bigobj-aarch64-little is needed or if it will be
supported in the future.

My first attempt to get gcc (I tried with source tarball 12.2.0) to configure
was changing the following line in gcc/config.gcc:

i[34567]86-*-mingw* | x86_64-*-mingw*)

to:

i[34567]86-*-mingw* | x86_64-*-mingw* | aarch64-*-mingw*)

but then I get the following error:

Unknown tune used in --with-tune=generic

What needs to be changed to get past that?

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=87334
             Target|                            |Aarch64-mingw

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I have not seen anyone step up to patch GCC for aarch64-mingw yet.
Most aarch64 developers don't use Windows at all. There is some support being
worked on for aarch64 darwin (Mac OS) though.

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

--- Comment #2 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
I would love to give it a go if only I knew where to add the support.

I actually got a Windows on ARM device hoping I could figure it out, bit it
looks I will need tome help.

The "Unknown tune used in --with-tune=generic" error is where I'm currently
stuck, and I couldn't figure out in which file(s) I need to address this.

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

--- Comment #3 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
Any pointers on which files to edit in order to support aarch64-mingw ?

I think it won't require reinventing the wheel as it will probably be a mix of
existing *-mingw and aarch64-* stuff...

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[zac.walker at linaro dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

Zac Walker <zac.walker at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zac.walker at linaro dot org

--- Comment #4 from Zac Walker <zac.walker at linaro dot org> ---
I have been working on an experimental aarch64-w64-mingw32 toolchain. It can
build several C libraries and small executables successfully. Currently parked
here on github:

https://github.com/ZacWalk/mingw-woarm64-build

It is based on previous work by Mark Harmstone and Jedidiah Thompson. I am
currently working on structured exception handling support. This seems to be
the main missing part - without it C++ exceptions do not work.

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

--- Comment #5 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
Thanks Zac, how can I see what you actually changed?
Is there a particular GCC version I can diff
https://github.com/ZacWalk/gcc-woarm64 against?

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[zac.walker at linaro dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

--- Comment #6 from Zac Walker <zac.walker at linaro dot org> ---
I have been rebasing regularly to keep all my changes on top of the commit log.
You can use github's compare url to combine my changes into a single diff
(based on commit hash). For example:

https://github.com/ZacWalk/gcc-woarm64/compare/06a0f07..0248264

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The change to libstdc++-v3/src/c++17/fast_float/fast_float.h should be done
upstream: https://github.com/fastfloat/fast_float

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[zac.walker at linaro dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

--- Comment #8 from Zac Walker <zac.walker at linaro dot org> ---
Thanks Jonathan. I am still in test and cleanup up mode but hope to start
upstreaming in a few weeks.

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2023-11-09
             Status|UNCONFIRMED                 |NEW

--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
.

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[brechtsanders at users dot sourceforge.net]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

--- Comment #10 from Brecht Sanders <brechtsanders at users dot sourceforge.net> ---
What is the status of GCC support for aarch64-w64-mingw32 ?

I just tried GCC 14 snapshot 20240414 and it looks like it's still not
supported.

Build fails with:
*** Configuration aarch64-w64-mingw32 not supported

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Brecht Sanders from comment #10)
> What is the status of GCC support for aarch64-w64-mingw32 ?
> 
> I just tried GCC 14 snapshot 20240414 and it looks like it's still not
> supported.
> 
> Build fails with:
> *** Configuration aarch64-w64-mingw32 not supported

Patches have started to be posted but won't be fully reviewed/committed until
after GCC 14 is released due to them coming in late (during stage 4) in the
release cycle (See https://gcc.gnu.org/develop.html for the full gcc
release/development cycle).

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[clyon at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

Christophe Lyon <clyon at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |clyon at gcc dot gnu.org

--- Comment #12 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Indeed the plan is to commit the first series
(https://gcc.gnu.org/pipermail/gcc-patches/2024-April/649261.html) once stage-1
re-opens (as approved in
https://gcc.gnu.org/pipermail/gcc-patches/2024-April/649299.html

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[unlvsur at live dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

--- Comment #13 from cqwrteur <unlvsur at live dot com> ---
/home/cqwrteur/toolchains_build/gcc/gcc/c-family/c-format.cc:5159:(.text+0x7c1):
undefined reference to `msformat_init()'
/usr/local/lib/gcc/x86_64-pc-linux-gnu/15.0.0/../../../../x86_64-pc-linux-gnu/bin/ld:
c-family/c-format.o: in function `cmp_attribs(char const*, char const*)':

Can you explain to me what is going on? Thank you!

[Bug target/108678] Windows on ARM64 platform target aarch64-w64-mingw32

[unlvsur at live dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108678

--- Comment #14 from cqwrteur <unlvsur at live dot com> ---
libgcc:

/home/cqwrteur/toolchains_build/gcc/libgcc/libgcov.h:49:10: fatal error:
sys/mman.h: No such file or directory
   49 | #include <sys/mman.h>
      |          ^~~~~~~~~~~~
compilation terminated.
make[4]: *** [Makefile:933: _gcov_interval_profiler.o] Error 1
make[4]: *** Waiting for unfinished jobs....