-
Notifications
You must be signed in to change notification settings - Fork 16
Open
Description
GOAL appears to have two formats, binary and textual. Both the binary format and in-memory data structures represent DeserializedNode.Tag as a 32-bit unsigned integer. However the GOAL textual format appears to support tags >32-bit. E.g.:
- http://storage2.spcl.ethz.ch/traces/ai/llama/Llama7B_N4_GPU16_TP1_PP1_DP16_BS32/llama.goal
- http://storage2.spcl.ethz.ch/traces/ai/llama/Llama7B_N4_GPU16_TP1_PP1_DP16_BS32/llama.bin
Line 7176456 of (1) has:
l100000: recv 788480b from 0 tag 21020814305 cpu 4 nic 0
but if you parse and interpret (2), you find this entry has the tag 3840945121. 3840945121 = 21020814305 & (2³² - 1). Maybe the GOAL binary format is intended to use a 64-bit tag field?
I’m basically reverse engineering here, so please let me know if I’ve mistaken something.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels