I've tried the newest windows installer ( "sdcc-20240729-14932-setup.exe" ). cc1 is still installed to sdcc/bin, not sdcc/libexec/sdcc .
Yes sdcc-snapshot-x86_64-w64-mingw32-20230707-14184 works well for me.
Here is package with all files used. All command I used can be found in the batch script files. The .a files are identical until it get corrupted in windows like sdar.exe rcDs testCore.a genericPrintSerial0.c.rel
Get it, I will try to compare the difference between the Mac and Win files with D flag later today when I get to the computer with the batch script.
Here are the 2 files causing trouble. I was using snapshot build.14184 Command was like sdar.exe rcs testCore11.a genericPrintSerial0.c.rel I tried again on Mac, that was totally fine. But on Windows, this command does not throw any error. And the .a file shrink from 160K to 6K. I think that is the moment it get corrupted as the text viewer can not see any instructions in that file anymore. The rcDs does not help.
Some update: The sdcc of windows and mac created a slight difference .o file in one of the .c file. So I used the .o file generated from mac as a start point to test sdar in mac and windows. Each .rel (adjusted CSEG only) is added to a library file, in each step, the .a file is backuped. So until the testCore11.a in win and mac both look OK. but when the genericPrintSerial0.c.rel is added. The testCore12.a mac file is still OK. But the testCore12.a win file lost content. The command I used was something...
Some update: The sdcc of windows and mac created a slight difference .o file in one of the .c file. So I used the .o file generated from mac as a start point to test sdar in mac and windows. Each .rel (adjusted CSEG only) is added to a library file, in each step, the .a file is backuped. So until the testCore11.a in win and mac both look OK. but when the genericPrintSerial0.c.rel is added. The testCore12.a mac file is still OK. But the testCore12.a win file lost content.
Windows specific sdar failure with modified CSEG