To add to Ben's response - the name of a function or variable that you see in the generated code is, currently, its name in Chapel code + some integer, for uniquifation + _chpl. The integer might persist from compilation to compilation, no guarantees whatsoever though. In the other direction, the function named this46 in C likely has 'proc this' in Chapel. You can find it, for example, by line number comments or #file directives in the generated C code, given the right chpl compiler options.
Vassily On 04/08/16 14:29, Hui Zhang wrote: > Hello, > > I'm curious about the definitions of the auto-gened Chapel internal > functions in the compiled code. I saw functions like "this*" called in the > code, which seem to be some helper functions to access the array/tuple > elements. > My question is: > 1. are the *names* of the internal functions deterministic ? or randomly > generated during compilation. Like here, are all "this*" functions always > generated for accessing the array/tuple elements ? > > Thanks ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/ gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532 _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
