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

[WongCK <won...@ya...>]

 I felt it was like double the time to compile the same code as compared to before.Did not measure it but so may be in the region of 50% may be more realistic.


    On Friday, 7 June 2024 at 01:45:24 am SGT, Miro Kropáček <mir...@gm...> wrote:  
 
 On Thu, 6 Jun 2024 at 17:23, Thorsten Otto <ad...@th...> wrote:


As far as i've seen, that mostly enable some assertion checks. That should normally be hardly noticable, given that the compiler is surely already not very fast on real hardware.

>From my experience on working on ScummVM, asserts did make a big difference. People normally (i.e. on PC) don't notice them (except some extreme cases) but on Atari, all it takes is one assert in an often-called inner loop and performance goes 50% down.



I have no problem removing that again, with the risc that if the compiler generates bad code, this will be harder to notice. In the worst case, it will cause you to hunt bugs in your code that are really just the compilers fault ;)

If you take into account that such a bug occurs maybe once per year, I think it's ok. We can always provide an additional build with the check(s) enabled when such situations occur.
-- 
http://mikro.atari.org_______________________________________________
Freemint-discuss mailing list
Fre...@li...
https://lists.sourceforge.net/lists/listinfo/freemint-discuss