Re: [Freemint-discuss] Debugging a problem in gcc-14

[Thorsten O. <ad...@th...>]

On Montag, 3. Juni 2024 14:16:45 CEST Miro Kropáček wrote:
> Did you report it upstream as well? So they know that their optimisation is
> not so great after all.

Yes, there was already an open bug report, so i added my findings there:

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

But if you look at the git log of the master tree, you will see that there 
have already been some fixes after the original patch, none of them fixed the 
current problem, and other targets than m68k were also affected.

>It was working pretty well but then Travis closed its doors and that was the 
end of it.

Maybe you can have a look at it again? Should not be too hard to convert the 
travis scripts to github actions. And all the native tools should be 
available, either old versions from sparemint, or newly compiled ones from my 
site. I think some of them aren't even needed, eg. perl & m4 are imho only 
needed to regenerate the configure scripts using autoconf, but that should not 
happen.

But Eero is right, qemu is not an option in our case. We need something that 
is able to run atari executables.