search for: framedrt

...      } This filled buffer is then passed to various functions, on it's journey handling data at various instance of time about frames. These functions use this buffer, by assiging to appropriate struct pointers (memory reusing probably).      frameDLt  = (FRAME_DATA*) &Data[MAX_SIZE];    frameDRt  = (FRAME_DATA*) &Data[3*MAX_SIZE]; Where frameDLt and frameDRt are struct pointers to "FRAME_DATA *frameDLt;" and "SBR_FRAME_DATA *frameDRt;"   The struct is defined as:    %struct._FRAME_DATA = type { i16, %struct._FRAME_INFO, [5 x i16], [2 x i16], [5 x i32], i32, i16, [...

...       } This filled buffer is then passed to various functions, on it's journey handling data at various instance of time about frames. These functions use this buffer, by assiging to appropriate struct pointers (memory reusing probably).    frameDLt  = (FRAME_DATA*) &Data[MAX_SIZE];    frameDRt  = (FRAME_DATA*) &Data[3*MAX_SIZE]; Where frameDLt and frameDRt are struct pointers to "FRAME_DATA *frameDLt;" and "SBR_FRAME_DATA *frameDRt;" The struct is defined as:  %struct._FRAME_DATA = type { i16, %struct._FRAME_INFO, [5 x i16], [2 x i16], [5 x i32], i32, i16, [48...

With reference to the previous query, I think, i miscalculated the offset, just recalculating. 1. without instruction combining coupling member variable, is at:   %struct._FRAME_DATA* %2, i32 0, i32 5   where "%2" is defined as:   %arrayidx3 = getelementptr inbounds i16* %Data, i32 1024, !dbg !446   %2 = bitcast i16* %arrayidx3 to %struct._FRAME_DATA*, !dbg !446 i.e. at 5 offset in