Add the GCC 13.4 release

[void2012]

The GCC 14 and GCC 15 constant evaluator engines are currently broken - they often segfault on very simple code that can be constant evaluated. I asked my friend to report a bug (I couldn't register the gcc bugzilla account myself) and the maintainers confirmed the bug is indeed happening.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123354
(not that this is just one example and I could find a lot, lot more examples of GCC ICE'ing on simple valid code)
which started because of the commit
https://gcc.gnu.org/cgit/gcc/commit/?id=9bc6b23d11697545e8a951ccd60691b1e58b98c2

The situation turned out to be sooo bad, it broke so much code for me I think on going back to GCC 13. But the last GCC 13 release of w64devkit was in April 2024. The changes in the w64devkit themselves are so good I want to have them alongside the GCC 13.4 compiler. Could you please add a 13.4 release as an alternative release? Thanks!

[Peter0x44]

wouldn't it be better to just apply a patch reverting that commit?

[void2012]

I have no clue I am no GCC developer :(

And it appears that only two lines of code lead to this disaster.

[void2012]

Maybe it isn't that easy to just remove the lines and expect everything to work. Maybe it's more nuanced than that. Anyway, I think on going back to GCC-13

[Peter0x44]

I posted my own analysis of the issue along with a patch that at least fixes the ICE for me on the bugzilla PR.
I don't think this is honestly a good enough reason to go to the effort of providing a gcc 13. I'm confident it can be fixed.

https://github.com/Peter0x44/w64devkit/actions/runs/20743952903/job/59556708034

You can download a build with the patch here.
LMK if it fixes anything. Or has other problems.

[void2012]

Alright, thanks anyway. Is anyone actually working on the fix? I saw your comment and you say that this is just a hack, is this actually going to be fixed in GCC-16 or patches for the GCC-14/15?

[Peter0x44]

I'm not even sure what I wrote is a hack. Reading more, it does seem like it might be the correct solution.
I'll post the patch later but I can't guarantee its inclusion in any version. I'm not a (professional) gcc developer.

[Peter0x44]

If you really want to speed things along, test the branch. Thanks.

[void2012]

Yes, thanks, once the release appears in your fork, I am going to download and test it.

[Peter0x44]

I'm not going to make a release out of it.
Go to the github actions run and find the "Upload artifact" section. The link to download it is there.

Note that you must be signed in github to do this.

[void2012]

Ah, I see, thanks.

[Peter0x44]

It's fixed upstream for gcc 16.