Bugzilla – Bug 73
Bytecode format inconsistent
Last modified: 2004-01-15 11:57:17
You need to log in before you can comment on or make changes to this bug.
All bytecode blocks are prefixed with their bytecode id and size and are aligned to a word boundary. The size is the number of bytes of the block excluding the padding. This is true for all blocks except the the MODULE_GLOBAL_INFO_BLOCK. Since this will require a bump of the bytecode version number, we should postpone its fix for just before the next release.
To be perfectly clear here, this does not effect the functionality of the bytecode format: It is a wart in the representation (which should be fixed).
For those interested in bytecode format changes, this patch should also be looked at: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20031201/009937.html http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20031201/009938.html -Chris
It looks like the next bytecode version will happen with 1.2, so this will get delayed until then. :( -Chris
This is finally fixed: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20040112/010812.html http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20040112/010813.html -Chris