employer
/
tame
1
0
Fork 0
Code Packages Releases Activity
tame/tamer/tests/xmli
History
Mike Gerwitz 9990be58a7 tamer: Lower sum expressions 
This was a fairly simple addition, since rate blocks already lower into sum
expressions; these are just non-identified.

This does emphasize that the nir::parse `ele_parse!` abstraction I spent so
much time on ended up not being a perfect fit, as it now has some
boilerplate after it was stripped of much of its capabilities some time ago.

Don't worry, `nir::air` and `asg::graph::xmli` will get cleaned up.

DEV-13708
 		2023-03-10 14:27:58 -05:00
..
.gitignore tamer: asg::graph::object::xir: Initial rate element reconstruction 2023-03-10 14:27:58 -05:00
README.md tamer: asg::graph::object::xir: Initial rate element reconstruction 2023-03-10 14:27:58 -05:00
expected.xml tamer: Lower sum expressions 2023-03-10 14:27:58 -05:00
src.xml tamer: Lower sum expressions 2023-03-10 14:27:58 -05:00
test-xmli tamer: asg::graph::object::xir: Initial rate element reconstruction 2023-03-10 14:27:58 -05:00

README.md

XMLI System Test

The xmli file is an intermediate file that serves as a handoff between TAMER and the XSLT-based compiler:

xml -> (TAMER) -> xmli -> (TAME XSLT) -> xmlo

TAMER gets the first shot at processing, and then the compilation process continues with the XSLT-based compiler. This allows TAMER to incrementally augment and manipulate the source file and remove responsibilities from TAME XSLT.

Tests in this directory ensure that this process is working as intended. TAMER's failure to perform a proper handoff will cause TAME XSLT to compile sources incorrectly, since TAMER will have rewritten them to something else.

This handoff is more than just echoing tokens back into a file---it derives a new program from the state of the ASG. This program may have a slightly different representation than the original sources, but it must express an equivalent program, and the program must be at least as performant when emitted by TAME XSLT.

Running Tests

Test are prefixed with test-* and are executable. They must be invoked with the environment variable PATH_TAMEC set to the path of tamec relative to the working directory.