[MLton-devel] experimental release of source-level profiling
Matthew Fluet
fluet@CS.Cornell.EDU
Mon, 20 Jan 2003 16:18:56 -0500 (EST)
> I've duplicated the problem and isolated the bug. It is happening
> because the native codegen is caching gcState.currentSource in a
> register. It should always be written to memory as soon as it is
> assigned, since the profile signal handler looks at it. I tried
> making its class GCStateVolatile, but that didn't seem to help. Is
> there some way of getting the behavior I need?
GCStateVolatile was supposed to ensure that it was written to it's memory
location every time it was modified. Do you have a small example that
exhibits the bug? Or any outstanding changes that affect it?
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel