daves Posted January 10, 2014 Share Posted January 10, 2014 I point m98 at something of interest and report it (two ways): m98->Gate3[0].MacroInA[0][3] m98 M98=-7077888 sys.m[98] Sys.M[98]=-7077888 Then I point m99 at m98 and report it (two ways): m99->sys.m[98] m99 M99=-7077888 sys.m[99] Sys.M[99]=nan Also note Sys.M[99].a=nan. It appears m99 is still working but no longer in the sys.m array, or the sys.m array has been corrupted. Is this as expected? I was experimenting with chaining variable definitions but don't think I will use that now (as I can't subsequently point m100 at sys.m[99] or m99 another way). Link to comment Share on other sites More sharing options...
steve.milici Posted January 13, 2014 Share Posted January 13, 2014 Access to M-variable structures in Power PMAC are actually functions so when you have a pointer to one the resolution of the address is not like a "true" structure. There are functions in the Power Pmac API Library that you can use, such as: GateArray1* GateArray2* GateArray3* Link to comment Share on other sites More sharing options...
Recommended Posts