public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "brechtsanders at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108678] New: Windows on ARM64 platform target aarch64-w64-mingw32 Date: Sun, 05 Feb 2023 14:43:03 +0000 [thread overview] Message-ID: <bug-108678-4@http.gcc.gnu.org/bugzilla/> (raw) 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?
next reply other threads:[~2023-02-05 14:43 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-05 14:43 brechtsanders at users dot sourceforge.net [this message] 2023-02-05 17:39 ` [Bug target/108678] " pinskia at gcc dot gnu.org 2023-02-05 18:19 ` pinskia at gcc dot gnu.org 2023-02-05 19:23 ` brechtsanders at users dot sourceforge.net 2023-06-24 20:14 ` brechtsanders at users dot sourceforge.net 2023-06-26 8:25 ` zac.walker at linaro dot org 2023-06-26 18:05 ` brechtsanders at users dot sourceforge.net 2023-06-26 20:34 ` zac.walker at linaro dot org 2023-06-26 22:05 ` redi at gcc dot gnu.org 2023-06-28 11:40 ` zac.walker at linaro dot org 2023-11-09 3:47 ` pinskia at gcc dot gnu.org 2024-04-17 20:15 ` brechtsanders at users dot sourceforge.net 2024-04-17 20:20 ` pinskia at gcc dot gnu.org 2024-04-18 9:14 ` clyon at gcc dot gnu.org 2024-05-14 8:08 ` unlvsur at live dot com 2024-05-14 9:56 ` unlvsur at live dot com 2024-06-05 13:39 ` Evgeny.Karpov at microsoft dot com
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=bug-108678-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).