From: Philipp K. K. <pk...@sp...> - 2012-01-22 17:19:13
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22.01.2012 17:50, Borut Ražem wrote: > On 22. 01. 2012 13:00, Philipp Klaus Krause wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> >> Dear sdcc developers, >> >> sdcc 3.1.0 has been released a while ago, and we've received some >> bug reports about bad bugs (wrong code being generated silently) >> since; some of them seem to be regressions. I've been adding them >> to >> https://sourceforge.net/apps/trac/sdcc/wiki/SDCC%203.2.0%20Release >> >> (except for those that have been fixed quickly), where they now sit >> alongside the postponed stuff from 3.1.0. The gbz80 port has made >> some progress, and code size and number of regression test >> failures are down a lot compared to 3.1.0. On the other hand I >> intend to work on some bigger things in spring and summer (stack >> allocation, coalescing and making the new register allocator work >> for another port, most likely the hc08 or hcs08), which is likely >> to break things. > > I assume that you'll make new branch(es) for the new stuff, so the > 3.2.0 release can be done from the svn head? The release canbe done from trunk; I haven't decided yet how many branches I will need; most likely one for the hc08 register allocator, but for the other stuff I might create new ones or use the existing stack-compact branch. I don't not know how well the work will progress, but maybe one of the branches will be ready for merge in march or so; it would be nice if the branch doesn't have to wait for too long before being merged then. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk8cRQAACgkQbtUV+xsoLprB7QCfeUlZQrBGeJhn3yoB6aWnMJEH Ag0An3xHyMJBwasnRGbrgofoN6w7yW+y =NcWj -----END PGP SIGNATURE----- |