This is the mail archive of the
mailing list for the Infinity project.
Language and note format changes coming up
- From: Gary Benson <gbenson at redhat dot com>
- To: infinity at sourceware dot org
- Date: Wed, 28 Oct 2015 10:24:50 +0000
- Subject: Language and note format changes coming up
- Authentication-results: sourceware.org; auth=none
- Organization: Red Hat UK Ltd, 64 Baker Street, 4th Floor, W1U 7DF, UK. Registered in England and Wales (3798903)
I don't know if anybody is playing with Infinity yet, but I have some
compatibility-breaking source language and note format changes in the
1. Operators with more than one argument (i.e. "name" and "cast"
will require a comma between their argument. This is for
consistency with #3. (I could make this optional, but pretty
much all source will need rewriting because of #2 so...)
2. Externals will no longer be pushed onto the stack at function
entry. You will need to use "load" to access them.
3. As a shortcut, several operators will gain an optional first
argument which incorporates a "load". e.g. instead of:
you may use the shortcut:
I'll likely add this to the branch operators too, so instead of:
you can do:
beq NULL, label
The folded loads are optional (i.e. you can still use the original
form) and both will generate the same bytecode.
This is all basically because of #2. Originally it seemed pushing
externals onto the stack at function entry would minimize the
differences between Infinity and "standard" DWARF, but actually it
just means you have more things to keep track of while writing the
notes. I'd thought this change would result in longer notes (because
of the extra operations to load the constants) but the ones I've
converted are shorter because the extra operations are offset by
not requiring so many stack-shuffling operations.
4. The "max_stack" field from the info chunk and the byteorder mark
field from the code chunk are being moved into a new code info
chunk with a type_id of 6.
5. The info chunk now contains only the function's signature. It's
being renamed the signature chunk with a type_id of 5.
6. The code chunk now contains only bytecode and has had its version
bumped to 2 to indicate this.
Aside from a cleaner structure, this change makes it possible to add
further information about the code. Previously this would have had
to go in the info chunk or in a new chunk--the code chunk was pretty
much unmodifyable. But that left the info chunk into a kind of
kitchen sink, full of stuff that should really have been somewhere
I8X 0.0.2 will support 0.0.1's note format (with info and v1 code
chunks) but this is deprecated and will be removed (probably just
after 0.0.2 is released but certainly before 1.0.0).
I8X 0.0.2 will push externals onto the entry stack only if the code
chunk in the note is version 1. This also is deprecated and will