search for: thecim

...y, PRT_IN PrtCimSpecificDataType opaqueData); }; /* struct PrtCodeInfoManagerFunctions */ /* Creates a new PrtCodeInfoManager and registers a set of callback functions belonging to it. */ PrtCodeInfoManager prtRegisterCodeInfoManager(PRT_IN const char *theCimName, PRT_IN struct PrtCodeInfoManagerFunctions theCimFns); /* * Register the block of code in [start..end] with the given PrtCodeInfoManager. * Returns True on success and False on failure (e.g., if the code's region overlaps that of already-registered code). * The opaqueData parameter is ass...

On 07.07.2011 08:31, Nate Fries wrote: > On 7/6/2011 6:24 PM, Talin wrote: >> The LLVM code generators and analysis passes have a much more >> thorough knowledge of SSA value lifetimes than frontends do, and >> therefore could avoid spilling and reloading of values when it wasn't >> needed. > Although this would indeed be nice, it is not done by similar >

...PRT_IN PrtCimSpecificDataType opaqueData);**** }; /* struct PrtCodeInfoManagerFunctions */**** ** ** ** ** /* Creates a new PrtCodeInfoManager and registers a set of callback functions belonging to it. */**** PrtCodeInfoManager prtRegisterCodeInfoManager(PRT_IN const char *theCimName, PRT_IN struct PrtCodeInfoManagerFunctions theCimFns);**** ** ** /***** * Register the block of code in [start..end] with the given PrtCodeInfoManager. **** * Returns True on success and False on failure (e.g., if the code's region overlaps that of already-registered code).**** * The...