Skip to content

Latest commit

 

History

History
113 lines (84 loc) · 4.15 KB

README.md

File metadata and controls

113 lines (84 loc) · 4.15 KB
Raw

Enfield

Build Status

This project was built on top of Bison (v3.0.2), Flex (2.5.39), and JsonCpp (v1.8.4).

Check out the documentation here!!

Building

Enfield uses CMake. So, in order to build this project, issue the following commands:

$ mkdir build && cd build
$ cmake ../ -DJSONCPP_ROOT=<path-to-jsoncpp-libs>
$ make

The script for finding JsonCpp is simple, so you will have to explicitly show Enfield where you installed it (the prefix folder).

Testing

Enfield uses the Google test framework to test its components. To enable automated tests, you should issue the cmake command as follows:

$ cmake ../ -DENABLE_TESTS=on
$ make && make test

It is possible to specify the root folder of the GTest framework. In order to do that, you should pass to cmake the option -DGTEST_ROOT=<path-to-gtest-libs>.

Compiling OpenQASM Programs

Suppose that you compiled enfield inside $BUILD_DIR folder. The enfield compiler will be located at $BUILD_DIR/tools. There you will find some programs, one of which is efd, the compiler itself.

The only required argument for compiling an OpenQASM program is the program itself. If you do not specify anything, enfield will compiile the input program with the default parameters. One can check the available parameter, as well as the default ones by executing the following command:

$ efd --help

The general form for compiling programs is:

$ efd -i <qasm-file> --alloc <allocator> --arch <architecture> -o <output-file>

For example: if we wanted to compile program tests/files/qft.qasm for architecture ibmqx2, using allocator wpm, while storing the compiled program inside qft_ibmqx2.qasm, we would have to execute the following:

$ efd -i tests/files/qft.qasm --alloc Q_wpm --arch A_ibmqx2 -o qft_ibmqx2.qasm

One could add the -stats flag, in order for enfield to print statistical data of the compilation, such as the weighted cost, depth, and number of gates of the compiled program.

It is also possible to feed the compiler a new architecture, and use it to compile the same program. So, for example, if we wanted to compile using architecture archfiles/tokyo.json, we would have to execute the following:

$ efd -i tests/files/qft.qasm --alloc Q_wpm --arch-file archfiles/tokyo.json -o qft_tokyo.qasm

Hacking

Even though this project is pretty new, it was designed to be extensible. So, here are a few tips in order to implement your own algorithm to your desired architecture. Below, I'll list some classes that are important to be aware of.

(Note that this is a (really brief) 'begginers guide', so you can do more stuff once you learn the code)

  • efd::QModule: The core class of enfield. It holds the AST preprocessed to be easier to use, as well as some other useful methods for modifying the AST. i.e.: insertSwapAfter; insertNodeAfter; replaceAllRegsWith, etc.

  • efd::Pass: Enfield is a pass-based compiler. Much like LLVM (but far from its user base), the transformations are implemented as Pass for QModules. There are plenty (ugly, though) so that you can implement yours! Good luck;

  • efd::QbitAllocator: This is the base class for implementing allocators. In order to implement your own, you should extend this class and implement the method allocate. This method is responsible for inserting swaps based on the QModule (that is given by parameter). After that, you have to surrender to the "beauty" of C++ macros, and modify the file Allocators.def, so that your allocator is available on command line;

  • Architectures.def: Take a look in this file in order to create the specification of other architectures. YES! More Macros! You will have to specify your architecture in a JSON format. Check the other architecture descriptions for a better understanding.