Aoineko

Hello, SDCC team, I’m active here asking for help or requesting new features, but I’ve never taken the time to thank you for all the work you’ve done. ^^ Thanks to SDCC, which I use in my MSXgl library, at least 27 new MSX games (a 80s-era machine based on the Z80) have been created over the past three years! A big thank you to you all for this great suite of tools that keeps getting better year after year. \o/ Here are a few of those games:

Hello, Will the "A2 Link-time elimination of unused functions and objects" feature be a priority for SDCC version 4.7.0?

I don't know how to mark this thread as "resolved"... but it is.

Hello, I updated my toolchain MSXgl with the last SDCC binaries. I use only the bare minimum to be able to compile MSX code: sdar, sdasz, sdcc, sdcpp, sdldz80 and... cc1. I got those binaries from the 4.6.0 official release package and checked that everything works fine on Windows (11) and Linux (through WSL2). But, a Linux user report an error linked to cc1 not found. Like in the official package, Linux's cc1 is located into the folder libexec\sdcc\amd64-unknown-linux2.5\12.1.0. Any idea of where...

I'm always using default option when comparing SDCC versions. I tried several complexity values, and you can indeed see that while SDCC 4.6 doesn't perform very well on the TheCastle project with the default settings compared to version 4.2, its performance gradually improves as the complexity increases (where version 4.2 doesn't seem to converge). 4.2 4.6 RC2 Compile options ---------------------------------------------------------------------- 31 515 32 482 default 31 458 31 934 --opt-code-speed...

I was able to investigate the issues I had found with 4.6.0 RC2: The crash in one of the test projects was not caused by SDCC 4.6 (the program only worked under specific timing conditions 🤦) The significative increase in the size of two projects appears to be due to 16-bit calculations that used to go through the HL/DE registers with SDCC 4.2 and now involve numerous accesses via the IX register. Not only does this increase the program's size, but it also slows it down significantly. I have three...

I was able to investigate the issues I had found with 4.6.0 RC2: The crash in one of the test projects was not caused by SDCC 4.6 (the program only worked under specific timing conditions 🤦) The significative increase in the size of two projects appears to be due to 16-bit calculations that used to go through the HL/DE registers with SDCC 4.2 and now involve numerous accesses via the IX register. Not only does this increase the program's size, but it also slows it down significantly. I have three...

I was able to investigate the issues I had found with 4.6.0 RC2: The crash in one of the test projects was not caused by SDCC 4.6 (the program only worked under specific timing conditions 🤦) The significative increase in the size of two projects appears to be due to 16-bit calculations that used to go through the HL/DE registers with SDCC 4.2 and now involve numerous accesses via the IX register. Not only does this increase the program's size, but it also slows it down significantly. I have three...