On Wednesday 24 June 2026 00:42:25 Kirill Makurin wrote: > Pali Rohár <[email protected]> wrote: > > > On Wednesday 17 June 2026 19:55:43 Pali Rohár wrote: > >> On Wednesday 17 June 2026 06:39:01 Kirill Makurin wrote: > >> > Pali Rohár <[email protected]> wrote: > >> > > I would propose to call this function at the beginning of main() before > >> > > declaring or initializing any variable, to ensure that it is always > >> > > called at the beginning. Initialization of variable could be done by > >> > > function call which could potentially cause assert/failure. > >> > > >> > I'm certain that I made sure that in every test which calls > >> > `mingw_test_init`, this it is the first function called. > > > > Now I have figured out that the test t_excpt_int_divzero.c does not do > > it for arm target. It does not call mingw_test_init at all. > > Originally, both t_excpt_int_divzero.c and t_excpt_int_overflow.c had calls to > > SetErrorMode(SetErrorMode(0) | SEM_NOGPFAULTERRORBOX); > > immediately after "if arm" block which returns 77 to indicate that the test > is skipped. I replaced it with a call to mingw_test_init(). > > As result, those tests may call `puts` before call to `mingw_test_init`. IMO, > this is not a big deal, but I can send a fixup if you insist. > > - Kirill Makurin
I understood. The point of this is to show why the mingw_test_init() call should be at the first line immediately in main() definition. To prevent in future putting any call between or to forgot that when modifying/extending e.g. that "if arm" block, it is also needed to ensure that mingw_test_init() is call. Everything is just to ensure easy debugging and avoid any pitfalls. _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
