From jean.claude.beaudoin at gmail.com Sat Jul 5 00:39:14 2014 From: jean.claude.beaudoin at gmail.com (Jean-Claude Beaudoin) Date: Fri, 4 Jul 2014 20:39:14 -0400 Subject: [Mkcl-announce] MKCL 1.1.9 is now available Message-ID: MKCL 1.1.9 is now available for general use. For the most part it is a compilation of minor bug fixes along with one notable sub-component upgrade, i.e.: the GC has been upgraded from bdwgc 7.2c to bdwgc 7.4 in hope it will be a better fit for the upcoming ARM/iOS/Android ports. One relevant change in the GC configuration happened on all MS-Windows versions where it is now hard configured to avoid the use of function SignalObjectAndWait since Microsoft has reneged on its promise of atomic behavior. If you observe a deadlock of MKCL 1.1.8 or earlier on MS-Windows 7 or later this would be a possible cause. You should then either upgrade to MKCL 1.1.9 or later, or set the environment variable MK_GC_MARKERS to 0 in order to prevent parallel marking and its use of SignalObjectAndWait. I hope that MKCL 1.1.9 will be the last in the MKCL 1.1.X line before the release of MKCL 1.2.0 in the coming months. Cheers, Jean-Claude Beaudoin -------------- next part -------------- An HTML attachment was scrubbed... URL: From santanu.chakrabarti at gmail.com Sat Jul 5 16:58:56 2014 From: santanu.chakrabarti at gmail.com (.Santanu Chakrabarti) Date: Sat, 5 Jul 2014 22:28:56 +0530 Subject: [Mkcl-announce] MKCL 1.1.9 is now available In-Reply-To: References: Message-ID: Thanks Jean!! I shall be downloading MKCL 1.1.9. However, I think it would be really helpful if this announcement email also had the download link. Regards Santanu On Jul 5, 2014 6:09 AM, "Jean-Claude Beaudoin" < jean.claude.beaudoin at gmail.com> wrote: > MKCL 1.1.9 is now available for general use. For the most part it is a > compilation of minor bug fixes along with one notable sub-component > upgrade, i.e.: the GC has been upgraded from bdwgc 7.2c to bdwgc 7.4 in > hope it will be a better fit for the upcoming ARM/iOS/Android ports. > > One relevant change in the GC configuration happened on all MS-Windows > versions where it is now hard configured to avoid the use of function > SignalObjectAndWait since Microsoft has reneged on its promise of atomic > behavior. If you observe a deadlock of MKCL 1.1.8 or earlier on MS-Windows > 7 or later this would be a possible cause. You should then either upgrade > to MKCL 1.1.9 or later, or set the environment variable MK_GC_MARKERS to 0 > in order to prevent parallel marking and its use of SignalObjectAndWait. > > I hope that MKCL 1.1.9 will be the last in the MKCL 1.1.X line before the > release of MKCL 1.2.0 in the coming months. > > Cheers, > > Jean-Claude Beaudoin > > -------------- next part -------------- An HTML attachment was scrubbed... URL: