The TIE compiler reads the description of the instruction extensions defined by the designer and generates both the hardware implementation and software tools for the new customized processor.
The PADS compiler reads these descriptions and generates a suite of useful data processing tools such as format translators, parsers, printers and even a query engine, all customized to the ad hoc data format in question.
Compilers read source code files as data and transform them into executables, which is just a conversion of data into another form.
One possible solution is that the compiler can read in a system constraint file, providing the system requirements, available hardware resources, targeted frequency, and so forth, based on which the configuration contexts are generated to satisfy these system requirements.
I don't think we actually knew at the time because when we started to build these language compilers, Dan was one page ahead of everybody reading his book on these compilers.
The compiler of the item you are now reading got in touch with his inner annoying-buzzword detector and, after a computer database search, came up with scads of references, from just this month alone.
One problem with the American-style crossword is that the letters often come in great blocks, reading up and down, which means that the compiler has to use some very strange words.
By allowing the compiler to schedule data transfers directly between function unit outputs and inputs, reading the value of previous computation from the register file becomes unnecessary.
So read your compiler outputs.
Even the index compilers will generally point to the importance of looking at the longer-term trends rather than reading too much into any one month.
