From: Borut R. <bor...@si...> - 2008-02-19 19:09:27
|
Dear sdcc developers and users, Maarten reminded me that nine months has passed but the child is not born yet ;-) So it's time to start thinking about the new sdcc release. I wold like to see some bugs being fixed, so I propose to create a list of high wanted bug fixes at http://sdcc.wiki.sourceforge.net/SDCC+2.8.0+Release. My idea is to give some time for bug fixing and then release the sdcc 2.8.0 in April or May. And an other good news: Maarten and I decided that applying Philipp Krause's patches is too big pain in the ass, so we invited him to join the sdcc development team :-D Everybody: say hello to Philipp! Borut |
From: Lin R. <wo...@di...> - 2008-02-19 20:34:17
|
Hello Philipp, so nice to see someone dedicate on Z80 in the team now! Woody AR1688 and PA1688 based IP phone mailing list -- http://groups.yahoo.com/group/pa1688/ VOIP and AR1688 BLOG -- http://aredfox.spaces.live.com/ MSN: wo...@ar... ----- Original Message ----- From: "Borut Razem" <bor...@si...> To: "Sdcc-Devel" <sdc...@li...>; "Sdcc-User" <sdc...@li...> Sent: Wednesday, February 20, 2008 3:09 AM Subject: [sdcc-devel] sdcc 2.8.0 release + new sdcc developer > Dear sdcc developers and users, > > Maarten reminded me that nine months has passed but the child is not > born yet ;-) > So it's time to start thinking about the new sdcc release. I wold like > to see some bugs being fixed, so I propose to create a list of high > wanted bug fixes at http://sdcc.wiki.sourceforge.net/SDCC+2.8.0+Release. > My idea is to give some time for bug fixing and then release the sdcc > 2.8.0 in April or May. > > And an other good news: Maarten and I decided that applying Philipp > Krause's patches is too big pain in the ass, so we invited him to join > the sdcc development team :-D > > Everybody: say hello to Philipp! > > Borut > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > sdcc-devel mailing list > sdc...@li... > https://lists.sourceforge.net/lists/listinfo/sdcc-devel |
From: Philipp K. K. <pk...@sp...> - 2008-02-19 22:06:18
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Borut Razem schrieb: > Dear sdcc developers and users, > > Maarten reminded me that nine months has passed but the child is not > born yet ;-) > So it's time to start thinking about the new sdcc release. I wold like > to see some bugs being fixed, so I propose to create a list of high > wanted bug fixes at http://sdcc.wiki.sourceforge.net/SDCC+2.8.0+Release. > My idea is to give some time for bug fixing and then release the sdcc > 2.8.0 in April or May. IMO the worst bugs are those where sdcc generates wrong code for valid C input. Next are those where sdcc crashes on valid C input. However these are probably the bugs that are the hardest to fix. If there are no objections I'll have a look at the bugs where sdcc crashes or generates wrong code on the Z80. I'd add those bugs that are still in current sdcc to the wiki page. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHu1KkbtUV+xsoLpoRAlmiAJ9yO4psc2xVNoKPGP737rINpVuVPACdG/se NkZeQDM/DFWs7xd32KmLys0= =+7ll -----END PGP SIGNATURE----- |
From: Borut R. <bor...@si...> - 2008-03-01 18:28:06
|
Quite some bugs were fixed lately, thanks to Philipp and Maarten. My plan is to give them an other week and then start with the standard release procedure: 9.3.2008: Release candidate 1 23.3.2008: Release candidate 2 30.3.2008: Final sdcc 2.8.0 release Any comments? Borut Borut Razem wrote: > Dear sdcc developers and users, > > Maarten reminded me that nine months has passed but the child is not > born yet ;-) > So it's time to start thinking about the new sdcc release. I wold like > to see some bugs being fixed, so I propose to create a list of high > wanted bug fixes at http://sdcc.wiki.sourceforge.net/SDCC+2.8.0+Release. > My idea is to give some time for bug fixing and then release the sdcc > 2.8.0 in April or May. > > And an other good news: Maarten and I decided that applying Philipp > Krause's patches is too big pain in the ass, so we invited him to join > the sdcc development team :-D > > Everybody: say hello to Philipp! > > Borut > |
From: Borut R. <bor...@si...> - 2008-03-07 18:17:29
|
I think we don't have any show stopper on the list, so we can proceed with the release plan I proposed. I'm publishing it on the SDCC 2.8.0 Release page. There are still 3 bugs on the SDCC 2.8.0 Release list, but none of them seems to be a regression from version 2.7.0, so we can mark them as postponed if they won't be fixed until the code freeze, which will happen during the RC1 release. Please hurry up if you have something to commit before the release or let me know if you don't agree with the release plan. Borut Borut Razem wrote: > Quite some bugs were fixed lately, thanks to Philipp and Maarten. My > plan is to give them an other week and then start with the standard > release procedure: > > 9.3.2008: Release candidate 1 > 23.3.2008: Release candidate 2 > 30.3.2008: Final sdcc 2.8.0 release > > Any comments? > > Borut > > > Borut Razem wrote: > >> Dear sdcc developers and users, >> >> Maarten reminded me that nine months has passed but the child is not >> born yet ;-) >> So it's time to start thinking about the new sdcc release. I wold like >> to see some bugs being fixed, so I propose to create a list of high >> wanted bug fixes at http://sdcc.wiki.sourceforge.net/SDCC+2.8.0+Release. >> My idea is to give some time for bug fixing and then release the sdcc >> 2.8.0 in April or May. >> >> And an other good news: Maarten and I decided that applying Philipp >> Krause's patches is too big pain in the ass, so we invited him to join >> the sdcc development team :-D >> >> Everybody: say hello to Philipp! >> >> Borut >> >> |
From: Maarten B. <sou...@ds...> - 2008-03-08 20:51:57
|
I want to thank all the developers who have helped to put the number of bugs down to 100 from an overwhelming 125 only a few weeks ago. > I think we don't have any show stopper on the list, so we can proceed > with the release plan I proposed. I'm publishing it on the SDCC 2.8.0 > Release page. > > There are still 3 bugs on the SDCC 2.8.0 Release list, but none of them > seems to be a regression from version 2.7.0, so we can mark them as > postponed if they won't be fixed until the code freeze, which will > happen during the RC1 release. > > Please hurry up if you have something to commit before the release or > let me know if you don't agree with the release plan. > > Borut > > > Borut Razem wrote: > > Quite some bugs were fixed lately, thanks to Philipp and Maarten. My > > plan is to give them an other week and then start with the standard > > release procedure: > > > > 9.3.2008: Release candidate 1 > > 23.3.2008: Release candidate 2 > > 30.3.2008: Final sdcc 2.8.0 release > > > > Any comments? > > > > Borut > > > > > > Borut Razem wrote: > > > >> Dear sdcc developers and users, > >> > >> Maarten reminded me that nine months has passed but the child is not > >> born yet ;-) > >> So it's time to start thinking about the new sdcc release. I wold like > >> to see some bugs being fixed, so I propose to create a list of high > >> wanted bug fixes at http://sdcc.wiki.sourceforge.net/SDCC+2.8.0+Release. > >> My idea is to give some time for bug fixing and then release the sdcc > >> 2.8.0 in April or May. > >> > >> And an other good news: Maarten and I decided that applying Philipp > >> Krause's patches is too big pain in the ass, so we invited him to join > >> the sdcc development team :-D > >> > >> Everybody: say hello to Philipp! > >> > >> Borut |
From: Borut R. <bor...@si...> - 2008-03-08 21:56:18
|
The number of open bugs is now below 100 :-) Thanks to all contributors from me too. I added 2 documentation enhancement requests to the SDCC 2.8.0 Release list: 1224821 <https://sourceforge.net/tracker/index.php?func=detail&aid=1224821&group_id=599&atid=536150> options in GBZ80 port not officially documented at http://sourceforge.net/tracker/index.php?func=detail&aid=1224821&group_id=599&atid=536150 1718191 <https://sourceforge.net/tracker/index.php?func=detail&aid=1718191&group_id=599&atid=536150> asxxxx options documentation at http://sourceforge.net/tracker/index.php?func=detail&aid=1224821&group_id=599&atid=536150 Any volunteer for the doc update? Maybe Frieder? This can be done after the code freeze... Borut Maarten Brock wrote: > I want to thank all the developers who have helped to > put the number of bugs down to 100 from an overwhelming > 125 only a few weeks ago. > > >> I think we don't have any show stopper on the list, so we can proceed >> with the release plan I proposed. I'm publishing it on the SDCC 2.8.0 >> Release page. >> >> There are still 3 bugs on the SDCC 2.8.0 Release list, but none of them >> seems to be a regression from version 2.7.0, so we can mark them as >> postponed if they won't be fixed until the code freeze, which will >> happen during the RC1 release. >> >> Please hurry up if you have something to commit before the release or >> let me know if you don't agree with the release plan. >> >> Borut >> >> >> Borut Razem wrote: >> >>> Quite some bugs were fixed lately, thanks to Philipp and Maarten. My >>> plan is to give them an other week and then start with the standard >>> release procedure: >>> >>> 9.3.2008: Release candidate 1 >>> 23.3.2008: Release candidate 2 >>> 30.3.2008: Final sdcc 2.8.0 release >>> >>> Any comments? >>> >>> Borut >>> >>> >>> Borut Razem wrote: >>> >>> >>>> Dear sdcc developers and users, >>>> >>>> Maarten reminded me that nine months has passed but the child is not >>>> born yet ;-) >>>> So it's time to start thinking about the new sdcc release. I wold like >>>> to see some bugs being fixed, so I propose to create a list of high >>>> wanted bug fixes at http://sdcc.wiki.sourceforge.net/SDCC+2.8.0+Release. >>>> My idea is to give some time for bug fixing and then release the sdcc >>>> 2.8.0 in April or May. >>>> >>>> And an other good news: Maarten and I decided that applying Philipp >>>> Krause's patches is too big pain in the ass, so we invited him to join >>>> the sdcc development team :-D >>>> >>>> Everybody: say hello to Philipp! >>>> >>>> Borut >>>> |
From: Maarten B. <sou...@ds...> - 2008-03-02 20:56:06
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head> <title></title> <meta http-equiv="content-type" content="text/html;charset=utf-8"/> <meta http-equiv="Content-Style-Type" content="text/css"/> </head> <body> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt">Hi,</span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt"><br /> </span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt">I don't think I'll have as much time next week as I've invested in SDCC lately. The list of bugs that I would like to see fixed before a release is still over 10 items long and I doubt that it is possible to fix them before any reasonable release date. Bottom line: I agree with this release plan.</span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt"><br /> </span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt">About the three still open tracker items on the wiki list:</span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt"><br /> </span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt">1875933  Evelyn jumps into the void: is still young and maybe z80-only</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt"><br /> </span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt">1579949  Fatal internal compiler error: seems z80- related only too</span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt"><br /> </span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt">1427663  SIGSEGV on static array of function pointers: is pic14 related and half unreproducable</span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt"><br /> </span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt">This last one should not hold up any release in my opinion.</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt"><br /> </span></font></div> <div align="left"><font face="Courier New" size="2"><span style="font-size:10pt">Maarten</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt"><br /> </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> Quite some bugs were fixed lately, thanks to Philipp and Maarten. My </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> plan is to give them an other week and then start with the standard </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> release procedure:</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> 9.3.2008: Release candidate 1</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> 23.3.2008: Release candidate 2</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> 30.3.2008: Final sdcc 2.8.0 release</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> Any comments?</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> Borut</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> Borut Razem wrote:</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > Dear sdcc developers and users,</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> ></span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > Maarten reminded me that nine months has passed  but the child is not </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > born yet ;-)</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > So it's time to start thinking about the new sdcc release. I wold like </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > to see some bugs being fixed, so I propose to create a list of high </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > wanted bug fixes at http://sdcc.wiki.sourceforge.net/SDCC+2.8.0+Release. </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > My idea is to give some time for bug fixing and then release the sdcc </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > 2.8.0 in April or May.</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> ></span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > And an other good news: Maarten and I decided that applying Philipp </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > Krause's patches is too big pain in the ass, so we invited him to join </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > the sdcc development team :-D</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> ></span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > Everybody: say hello to Philipp!</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> ></span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> > Borut</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> >   </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> </span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> -------------------------------------------------------------------------</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> This SF.net email is sponsored by: Microsoft</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> Defy all challenges. Microsoft(R) Visual Studio 2008.</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> _______________________________________________</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> sdcc-devel mailing list</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> sdc...@li...</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> https://lists.sourceforge.net/lists/listinfo/sdcc-devel</span></font></div> <div align="left"><font face="Arial" color="#7f0000" size="2"><span style="font-size:10pt">> </span></font></div> <div align="left"><font face="Arial" size="2"><span style="font-size:10pt"><br /> </span></font></div> <div align="left"></div> </body> </html> |
From: Borut R. <bor...@si...> - 2008-03-02 22:37:12
|
Philipp, can you confirm (or deny) that the first two are z80 specific? Borut Maarten Brock wrote: > Hi, > > I don't think I'll have as much time next week as I've invested in > SDCC lately. The list of bugs that I would like to see fixed before a > release is still over 10 items long and I doubt that it is possible to > fix them before any reasonable release date. Bottom line: I agree with > this release plan. > > About the three still open tracker items on the wiki list: > > 1875933 Evelyn jumps into the void: is still young and maybe z80-only > > 1579949 Fatal internal compiler error: seems z80- related only too > > 1427663 SIGSEGV on static array of function pointers: is pic14 > related and half unreproducable > > This last one should not hold up any release in my opinion. > > Maarten > > > Quite some bugs were fixed lately, thanks to Philipp and Maarten. My > > plan is to give them an other week and then start with the standard > > release procedure: > > > > 9.3.2008: Release candidate 1 > > 23.3.2008: Release candidate 2 > > 30.3.2008: Final sdcc 2.8.0 release > > > > Any comments? > > > > Borut > > > > > > Borut Razem wrote: > > > Dear sdcc developers and users, > > > > > > Maarten reminded me that nine months has passed but the child is not > > > born yet ;-) > > > So it's time to start thinking about the new sdcc release. I wold like > > > to see some bugs being fixed, so I propose to create a list of high > > > wanted bug fixes at > http://sdcc.wiki.sourceforge.net/SDCC+2.8.0+Release. > > > My idea is to give some time for bug fixing and then release the sdcc > > > 2.8.0 in April or May. > > > > > > And an other good news: Maarten and I decided that applying Philipp > > > Krause's patches is too big pain in the ass, so we invited him to join > > > the sdcc development team :-D > > > > > > Everybody: say hello to Philipp! > > > > > > Borut > > > > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2008. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > sdcc-devel mailing list > > sdc...@li... > > https://lists.sourceforge.net/lists/listinfo/sdcc-devel > > > |
From: Philipp K. K. <pk...@sp...> - 2008-03-07 16:29:48
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Borut Razem schrieb: >> >> 1875933 Evelyn jumps into the void: is still young and maybe z80-only It's an old bug, but difficult to reproduce. I've seen it once in a while, but I only opened a bug report when I was able to create a small code sample to reproduce the bug. evelyn.c attached to the bug report will reproduce the bug on z80 and gbz80. On hc08 it makes the compiler crash. It compiles on other architectures. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH0W1ebtUV+xsoLpoRAvWYAJsHawcQJAgCOjAqvo10tFuoScPcrACfV6G5 qyWZtKklIzgBCYsO5nTtCn0= =+He5 -----END PGP SIGNATURE----- |
From: Philipp K. K. <pk...@sp...> - 2008-03-07 16:34:00
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Borut Razem schrieb: >> 1579949 Fatal internal compiler error: seems z80- related only too I think this one is z80-related. At least it compiles on mcs51, hc08, ds400. It fails on z80 and gbz80. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH0W5ubtUV+xsoLpoRAuTGAJ9xcmBlWx8AJ38nkpIYD6FCAM4aVwCg4dEk L4crFOk97dLpXKPaqsxOjzk= =W7ry -----END PGP SIGNATURE----- |
From: Philipp K. K. <pk...@sp...> - 2008-03-08 18:50:50
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Borut Razem schrieb: > Philipp, can you confirm (or deny) that the first two are z80 specific? > > >> >> [...] >> >> 1579949 Fatal internal compiler error: seems z80- related only too >> It is not Z80 specific. It affects all ports, however the symptoms are different. Most ports generate a few instructions that serve no purpose, on z80 and gbz80 a jump to a nonexisting label is generated, hc08 has an assertion that catches this (thus making the compile fail). I'll look into it a bit more and add further information to the bug report. Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH0t/ybtUV+xsoLpoRApd2AKDPQJiWB5DfbIOKnDVl23n+O3GsEQCg5HVJ wPHQgFt8vlD+Fn8u1lyD3PY= =6RSP -----END PGP SIGNATURE----- |
From: Raphael N. <rn...@we...> - 2008-03-07 22:28:51
|
Hi, > About the three still open tracker items on the wiki list: > > 1875933 Evelyn jumps into the void: is still young and maybe z80-only > > 1579949 Fatal internal compiler error: seems z80- related only too > > 1427663 SIGSEGV on static array of function pointers: is pic14 related > and half unreproducable > > This last one should not hold up any release in my opinion. The good news is that I just committed a fix for this last 1427663 SIGSEGV-issue, which was already down to an 'array not initialized properly' issue. Fix committed in r5074. Regards, Raphael |
From: Borut R. <bor...@gm...> - 2011-10-14 20:09:42
|
Dear sdcc developers and users, I'm glad to announce a new sdcc developer: Leland Morrison. He has done most of the work in the Rabbit 2000 port: the target code generator, sdasrab assembler and ucsim support. Everybody: say hello to Leland! Thanks to Philipp and Leland sdcc now supports two new targets: Z180 and Rabbit 2000. Both of them IMHO can be cosidered as "mature" since they both pass the regression tests. P.S.: snapshot builds seems to be finally stable again, after some "hiccups" last week. Borut |