ira for Windows

[jotd]

I used V2.10. I used kickstart 1.1 (PAL) A1000, with just "ira -offset=$FC0000 -a kick11.rom" no fancy stuff

[phx]

Oh, indeed! There was a bug in the automatic ROMTag detection, when the Init-vector is NULL. Fixed. The current beta source is here:
http://sun.hasenbraten.de/~frank/TEST/ira_210beta.lha

Thanks for reporting!

[jotd]

yes, tested and working. Thanks!

[hop]

I've just built ira V2.10 using Visual Studio 2022 on Windows. To keep the debugger happy, I had to fix a few warnings:

1>C:\dev\Amiga\ira\ira_2.c(213): warning C4700: uninitialized local variable 'm' used
1>C:\dev\Amiga\ira\ira_2.c(438): warning C4700: uninitialized local variable 'refptr' used
1>C:\dev\Amiga\ira\ira.c(1536): warning C4700: uninitialized local variable 'adr' used
1>C:\dev\Amiga\ira\ira.c(3217): warning C4700: uninitialized local variable 'reg' used
1>C:\dev\Amiga\ira\ira.c(1908): warning C4700: uninitialized local variable 'reg' used
1>C:\dev\Amiga\ira\ira.c(1909): warning C4700: uninitialized local variable 'adr' used

These all use the same pattern, which I have never seen before. For example ira_2.c(438):

uint32_t ptr, refptr = refptr, functable, module = 0;

which causes the debugger to throw an exception:

Run-Time Check Failure #3 - The variable 'refptr' is being used without being initialized.

Is it safe to fix these warnings, or are they there for a reason? Is this a historical way of initialising to zero perhaps?