Switching from i686-mingw32 to x86_64-w64-mingw32?

Zhongteng Gui via Gcc <[email protected]>
Newsgroups gmane.comp.gcc.devel
Message-ID <SL2P216MB22713567DF1A0CC2252CC300EFD82@SL2P216MB2271.KORP216.PROD.OUTLOOK.COM>
Hi, I'm not sure whether this should be asked here, but I can't find a more
appropriate list.

I was reading https://gcc.gnu.org/gcc-17/criteria.html, and found that
i686-mingw32 is listed as a secondary platform, while x86_64-w64-mingw32 is not
listed.

It seemes that i686-mingw32 has been here since gcc-5 (actually the primary
platform list and secondary platform list only slightly changed from gcc-5 to
gcc-17). However, i686-mingw32 itself is actually not a valid *triplet*. And
regarding of i686-w64-mingw32, which it likely actually refers to, MSYS2 (the
main distribution of GCC on Windows) has deprecated MINGW32 (the only
environment with i686-w64-mingw32 triplet) since 2023-12-13 [1]. The default
environment of MSYS2 (previously MINGW64 and now UCRT64) all uses
x86_64-w64-mingw32.

Considering that i686 devices are very rare compared to x86_64 nowadays, I think
it would be better to switching from i686-mingw32 to x86_64-w64-mingw32 as a
secondary platform. Maybe i686-pc-cygwin could also be replaced by x86_64-pc-cygwin.

[1]: https://www.msys2.org/docs/environments/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.