[M3devel] cm3cg coverage/profiling features?

[Darko Volaric]

Sorry, I was distracted by a phone call before - that is the compiler
that exhibits the behaviour. Previous to that I was using something
that was compiled in 2010, so not very helpful for pinpointing.

On 8/12/15, Antony Hosking <hosking at purdue.edu> wrote:
> Are you saying that the behavior was still working as of d5.9.0?
> Or is that the version you are currently using in which it no longer does
> what you want?
> We should be able to figure out what commit broke things if we can pinpoint
> a time when it worked.
>
>> On Aug 13, 2015, at 10:27 AM, Darko Volaric <lists at darko.org> wrote:
>>
>> I'm using:
>>
>> Critical Mass Modula-3 version d5.9.0
>>
>>   last updated: 2010-07-21
>>
>>   compiled: 2014-08-27 19:15:04
>>
>>   configuration: /usr/local/cm3/bin/cm3.cfg
>>
>>   host: AMD64_DARWIN
>>
>>   target: AMD64_DARWIN
>>
>>
>>
>>
>> On Wed, Aug 12, 2015 at 5:23 PM, Antony Hosking <hosking at purdue.edu
>> <mailto:hosking at purdue.edu>> wrote:
>> I wasn’t aware this had changed.
>> When was this regression introduced?
>>
>>> On Aug 13, 2015, at 2:11 AM, Darko Volaric <lists at darko.org
>>> <mailto:lists at darko.org>> wrote:
>>>
>>> For instance, cm3 used to keep on compiling files after errors were
>>> found. Now it seems to stop after one module. That loss of functionality
>>> seriously reduces productivity. I couldn't find any switch to reverse the
>>> change. When was this change decided? Is there a way to restore it?
>>
>>
>
>