You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The various strings used in vmon are what C would call "read only data", which the linker would eventually merge into the .text segment. There might be some "locality of reference" advantages to putting the strings in .text or .rodata (I guess because of the inline nature of the cmd_xx files, using a separate segment has advantages over just using .text)
On "real hardware", .text and .rodata would go into flash/rom, a significant advantage over .data (in RAM) that would need to be copied at startup and/or manged WRT sharing RAM space with the application.
The text was updated successfully, but these errors were encountered:
The various strings used in vmon are what C would call "read only data", which the linker would eventually merge into the .text segment. There might be some "locality of reference" advantages to putting the strings in .text or .rodata (I guess because of the inline nature of the cmd_xx files, using a separate segment has advantages over just using .text)
On "real hardware", .text and .rodata would go into flash/rom, a significant advantage over .data (in RAM) that would need to be copied at startup and/or manged WRT sharing RAM space with the application.
The text was updated successfully, but these errors were encountered: