[M3devel] cm3cg coverage/profiling features?

[Jay K]

(Note: This was meant to report the unit path but I failed to commit that. This is good enough for today. Later...)




From: jay.krell at cornell.edu
CC: hosking at purdue.edu; lists at darko.org; jay.krell at cornell.edu; m3devel at elegosoft.com
Subject: Re: [M3devel] cm3cg coverage/profiling features?
Date: Thu, 13 Aug 2015 10:34:26 -0700
To: jay.krell at cornell.edu

Sorry my mistake in 2013.
Fixed:
https://github.com/modula3/cm3/commit/ff9855193deeb4c4edde3fe51103f56438ab3206

 - Jay
On Aug 12, 2015, at 8:43 PM, Jay <jay.krell at cornell.edu> wrote:

"Yes".
 I will try to figure it out. My changes (that I remember!) were to add C mode. We also have the parallel backend change, off by default.

I'd like moving a module between packages to work, correctly incrementally. Like when I moved QPath from circa m3quake to circa m3middle (I don't remember exactly but it is obvious by the inconsistency in module prefix correlation to package -- I didn't rename the module.)

 - Jay
On Aug 12, 2015, at 7:06 PM, Antony Hosking <hosking at purdue.edu> wrote:

Jay, I know you made some changes to the builder at some point.  Can we try to pinpoint when this regression occurred?
On Aug 13, 2015, at 12:05 PM, Darko Volaric <lists at darko.org> wrote:Sorry, I was distracted by a phone call before - that is the compilerthat exhibits the behaviour. Previous to that I was using somethingthat 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?
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20150813/08907d89/attachment-0002.html>