From: Philipp K. K. <pk...@sp...> - 2018-03-23 13:09:42
|
SDCC 3.7.0 has been released about one month ago. It was a source-only release. Our download statistics show that about of the downloads are Windows binaries, and thus 3.6.0. For mcs51, going from 3.6.0 to 3.7.0 brought some code size regressions, which have been resolved. The number of bug reports after 3.7.0 was low, and the few regressions reported have been fixed. So, IMO, there are reasons to aim for a 3.8.0 release that includes binaries soon and SDCC is in a reasonable state. Most of the tasks for the 3.8.0 release could be postponed to 3.9.0. Before 3.8.0 we'd still have to: * Get snapshots for x86 Linux, x86 and amd54 Windows and macOS (which arch?) to build. * Get the valdiag failures down to 0. There are also a few tasks which are not strictly necessary, but IMO should be done before 3.8.0 if possible: * Fully implement the large memory model for stm8. * Fix mcs51 bugs #2540, #2669. * Bugs #2704, #2702, #2709 (which I just added to the 3.8.0 task list on the wiki; all of them result in silent generation of broken code) How about aiming for late April for the RC, and a Release early in May? Philipp |