Re: changes requesting for GCC 17 Release Criteria (secondary targets)

On 3/24/26 08:36, LIU Hao wrote:
> ? 2026-3-24 10:52, Andrew Pinski via Gcc ??:
>> Also `i686-mingw32` should be swapped out with `x86_64-mingw`. I don't
>> think 32bit mingw is being testing these days only 64bit.
> 
> I would like to suggest adding `x86_64-w64-mingw32`, while changing `i686-mingw32` to `i686-w64-mingw32`.
> 
> `i686-mingw32` references the old mingw.org. They have lost control of their domain name, and osdn.net
> which hosts their project has been down since months ago.
> 
> Please keep `i686-w64-mingw32`.
> 
> As both `{i686,x86_64}-pc-linux-gnu` are primary platforms, I don't see why `i686-w64-mingw32` can't be a
> secondary platform. Almost all distributions of mingw-w64 provide both i686 and x86-64 builds: MSYS2,
> Debian, ArchLinux, Ubuntu, mingw-builds, winlibs, and w64devkit. And I also build i686 myself. It won't
> go away very soon.
> 
> 

Agreed, please keep i686-w64-mingw32 in secondary, the "w64" vendor is 
used to identify mingw-w64 based targets. It is mostly used to produce 
32-bit programs for Windows even if gcc itself is not running on 32-bit 
Windows.

>> Also I propose removing `i686-pc-cygwin`, I have not seen any recent
>> work on 32bit x86 cygwin or testresults.
> 
> I suggest swapping `x86_64-pc-cygwin` in.
> 
> Cygwin 3.4+ since 2022-11 is x86-64 only. As a downstream fork of Cygwin, MSYS2 is also x86-64 only. Both
> are key infrastructure for building GNU software on Windows, including GCC itself.
> 
> 

This is correct, 32bit i686-pc-cygwin is no longer an active project and 
only available through historical archives.