Feature #176

Feature #108: Fixed-size object IDs

objid_t: tracing infrastructure should use objid_t

Added by Ramprasad Venkataraman over 6 years ago. Updated almost 2 years ago.

In Progress
Target version:
Start date:
Due date:
% Done:



Once the basic objid_t scaffolding is available (#170), the impacts on the tracing infrastructure and projections logs should be audited. Specifically, Tracing routines on the message send and delivery paths might only have an objid_t available at that point in the code. For eg look at getProjectionID(). Hence, the benefits of managing all the tracing using objid_t should be evaluated. Implementation decisions should be made accordingly.


#1 Updated by Ramprasad Venkataraman about 6 years ago

xi-symbol.C: generated tracing code uses ForArrayEltMsg explicitly, which is fine for now (so the tracing infrastructure won't get confused), but should eventually distinguish the ForIDedObjMsg case.

#2 Updated by Phil Miller almost 6 years ago

  • Target version changed from 6.6.0 to 6.7.0

This won't be ready for 6.6, so push it back.

#3 Updated by Phil Miller about 4 years ago

  • Assignee changed from Yanhua Sun to Ronak Buch

#4 Updated by Phil Miller almost 4 years ago

  • Target version changed from 6.7.0 to 6.8.0

#5 Updated by Sam White over 2 years ago

  • Category set to Tracing

#6 Updated by Ronak Buch over 2 years ago

  • Status changed from New to In Progress

#7 Updated by Phil Miller about 2 years ago

  • Target version changed from 6.8.0 to 6.9.0

#8 Updated by Ronak Buch almost 2 years ago

  • Target version deleted (6.9.0)

This is implicitly dependent on 64-bit ID, which is somewhat unstable according to Eric Mikida, so it's been waiting for that. It seems that it could be added for array elements now, but the intention was to wait until the ID stuff was stable for all kinds of chares.

Also available in: Atom PDF