[MLton-devel] experimental release of source-level profiling

Stephen Weeks MLton@mlton.org
Tue, 21 Jan 2003 12:43:16 -0800

> > I checked in the change to make gcState.currentSource volatile.
> > Running a MLton with that change, compiling any example with
> > 	-profile time -profile-stack true -profile-basis true
> > should show the problem.  I'm testing it on wc-scanStream.  Here is
> > the problematic Machine code and the assembly produced by the native
> > codegen.  Note that the assembly stores $0x13E into %edi, but does not
> > write it to memory.  So, the call to GC_profileEnter sees the wrong
> > currentSource.
> O.k.  I don't have time to look at it today, but I see the problem and
> will think about a solution.

Don't work on it too hard, unless it was a general bug with
GCStateVolatile that needs fixed.  I'm working on another solution
that avoids the use of currentSource entirely.

This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
MLton-devel mailing list