Monash University Faculty of Information Technology 2nd Semester 2023

FIT2014

Assignment 2

Regular Languages, Context-Free Languages, Lexical analysis, Parsing, Turing machines and Quantum Computation

DUE: 11:55pm, Friday 6 October 2023

In these exercises, you will

• implement a lexical analyser using lex (Problem 3);

• implement parsers using lex and yacc (Problems 1–6);

• program a Turing machine (Problem 7);

• learn about some aspects of quantum circuits and quantum registers, by applying our methods to calculations with them (Problems 2–7);

• practise your skills relating to context-free languages (Problem 8).

Solutions to Problem 7 must be implemented in the simulator Tuatara. We are providing version 2.1 on Moodle under week 8; the file name is tuatara-monash-2.1.jar. You must use exactly this version, not some other version downloaded from the internet. Do not unpack this file. It must be run directly using the Java runtime.

How to manage this assignment

• You should start working on this assignment now and spread the work over the time until it is due. Do as much as possible before week 10.

• Don’t be deterred by the length of this document! Much of it is an extended tutorial to get you started with lex and yacc (pp. 7–11) and documentation for functions, written in C, that are provided for you to use (pp. 12–17); some matrices and sample outputs also take up a fair bit of space. There is an optional three-page introduction to some of the basics of quantum computing (pp. 17–19), which is there for those who are interested in knowing more but is not required for this assignment. Although lex and yacc are new to you, the questions about them only require you to modify some existing input files for them rather than write your own input files from scratch.

• The tasks required for the assignment are on pp. 3–6.

For Problems 1–5, read the background material on pp. 7–11.

For Problems 2–6, also read the background material on pp. 12–17. For Problem 7, read the background material on p. 21.

For Problem 8, read the background material on p. 22.

Instructions

Instructions are mostly as for Assignment 1, except that some of the filenames have changed, and now each Problem has its own directory. To begin working on the assignment, download the workbench asgn2.zip from Moodle. Create a new Ed Workspace and upload this file, letting Ed automatically extract it. Edit the student-id file to contain your name and student ID. Refer to Lab 0 for a reminder on how to do these tasks.

Open a terminal and change into the directory asgn2. You will find three files already in the directory: plus-times-power.l, plus-times-power.y, and quant.h. You will not modify these files directly; you will make copies of the first two and modify the copies, while quant.h must remain unaltered (although it’s ok to have copies of it in other directories).

1

You need to construct new lex files, using plus-times-power.l as a starting point, for Problems 1, 3, 4 & 5, and you’ll need to construct a new yacc file from plus-times-power.y for Problems 4 & 5. Your submission must include:

• the file student-id, edited to contain your name and student ID

• a lex file prob1.l which should be obtained by modifying a copy of plus-times-power.l

• a PDF file prob2.pdf which should contain your solution to Problem 2

• a lex file prob3.l which should also be obtained by modifying a copy of plus-times-power.l • a lex file prob4.l which should be obtained by modifying a copy of prob3.l

• a yacc file prob4.y which should be obtained by modifying a copy of plus-times-power.y • a lex file prob5.l which should be obtained by modifying a copy of prob4.l

• a yacc file prob5.y which should be obtained by modifying a copy of prob4.y

• a text file prob6.txt which should contain ten lines, being your solution to Problem 6

• a Tuatara Turing machine file prob7.tm

• a PDF file prob8.pdf which should contain your solution to Problem 8.

The original directory structure and file locations must be preserved. For each problem, the files you are submitting must be in the corresponding subdirectory, i.e. problemx for Problem x.

Each of these problem subdirectories contains empty files with the required filenames. These must each be replaced by the files you write, as described above. Before submission, check that each of these empty files is, indeed, replaced by your own file.

To submit your work, download the Ed workspace as a zip file by clicking on “Download All” in the file manager panel. The “Download All” option preserves the directory structure of the zip file, which is required to aid the marking process. You must submit this zip file to Moodle by the deadline given above.

2

Assignment tasks

First, read about “Lex, Yacc and the PLUS-TIMES-POWER language” on pp. 7–11.

Now refer to the document “Quantum circuits, registers and the language QUANT”, pages 12–17. In fact, for Problem 2, you can focus just on pages 15–17 and the language QCIRC.

   Problem 1. [2 marks]

Construct prob1.l, as described on pp. 9–11, so that it can be used with plus-times-power.y to build a parser for PLUS-TIMES-POWER.

    Problem 2. [3 marks]

Write a Context-Free Grammar for the language QCIRC over the ten-symbol alphabet

{I, H, X, Z, CNOT, TOF, *, ⊗, (, ) }. It can be typed or hand-written, but must be in PDF format and saved as a file prob2.pdf.pdf.

Now we use some very basic regular expressions (in the lex file, prob3.l) and a CFG (in the yacc file, prob4.y) to construct a lexical analyser (Problem 3) and a parser (Problem 4) for QCIRC.

   Problem 3. [3 marks]

Using the file provided for PLUS-TIMES-POWER as a starting point, construct a lex file, prob3.l, and use it to build a lexical analyser for QCIRC.

You’ll need to introduce simple regexps for the various tokens, among other things.

Sample output:

$ ./a.out

CNOT* ( H (x)I)

Token: CNOT; Lexeme: CNOT

Token and Lexeme: *

Token and Lexeme: (

Token: H; Lexeme: H

Token: KRONECKERPROD; Lexeme: (x) Token: I; Lexeme: I

Token and Lexeme: )

Token and Lexeme: <newline> Control-D

3

   Problem 4. [6 marks]

Make a copy of prob3.l, call it prob4.l, then modify it so that it can be used with yacc. Then construct a yacc file prob4.y from plus-times-power.y. Then use these lex and yacc files to build a parser for QCIRC that can correctly evaluate any expression in that language.

Note that you do not have to program any of the quantum expression functions yourself. They have already been written: see the Programs section of the yacc file. The actions in your yacc file will need to call these functions, and you can do that by using the function call for pow(. . . ) in plus-times-power.y as a template.

The core of your task is to write the grammar rules in the Rules section, in yacc format, with associated actions, using the examples in plus-times-power.y as a guide. You also need to do some modifications in the Declarations section; see page 10 and further details below.

When entering your grammar into the Rules section of prob4.y, it is best to leave the existing rules for the nonterminal start unchanged, as this has some extra stuff designed to allow you to enter a series of separate expressions on separate lines. So, take the Start symbol from your grammar in Problem 2 and represent it by the nonterminal line instead of by start.

The specific modifications you need to do in the Declarations section should be:

• You need a new %token declaration for the tokens I, H, X, Z, CNOT, TOF, and KRONECKERPROD. These have the same structure as the line for the NUMBER token, except that “num” is replaced by “str” (since each of the above tokens represents a string, being names of matrices, registers or operations, whereas NUMBER represents a number).

• You should include each of our two matrix operations, * (multiplication) and KRONECKERPROD (the Kronecker product, ⊗), in a %left or %right statement. Such a statement specifies when an operation is left- or right-associative, i.e., whether you do multiple consecutive operations left-to-right or right-to-left. Mathematically, for * and ⊗, it doesn’t matter. So, for these, you can use either %left or %right. But you should do one of them, because it helps the parser determine an order in which to do the operations and removes some ambiguity. For operations whose %left or %right statements are on different lines, the operations with higher precedence are those with higher line numbers (i.e., later in the file). Ordinary matrix multiplication should have higher precedence than Kronecker product.

• For nonterminal symbols, you can include a %type line that declares its type, i.e., the type of value that is returned when an expression generated from this nonterminal is evaluated. E.g.,

           %type <qmx> start here

Here, “qmx” is the type name we are using for quantum matrices. The various type names can be seen in the %union statement a little earlier in the file. But you do not need to know how that works in order to do this task.

• You should still use start as your Start symbol. If you use another name instead, you will need to modify the %start line too.

Sample output:

$ ./a.out

CNOT* ( H (x)I) 4x4 matrix:

0.707107

0.000000

0.000000

0.707107

0.000000

0.707107

0.707107

0.000000

0.707107

0.000000

0.000000

-0.707107

0.000000

0.707107

-0.707107

0.000000

Control-D

4

   Problem 5. [5 marks]

Make a copy of prob4.l, call it prob5.l. Also, make a copy of prob4.y, call it prob5.y. Then modify these lex and yacc files further to build a parser for QUANT that can correctly evaluate any expression in that language.

Again, the core of your task is to write the grammar rules in the Rules section, in yacc format with associated actions, in prob5.y. You will also need new tokens KET0 and KET1, which represent k0 and k1 respectively. These tokens need appropriate rules in prob5.l and declarations in prob5.y, and you will use them in the grammar.

    Problem 6. [5 marks]

In the problem6 directory you will find a file, prob6.awk. This is an awk program for converting your student ID number to a particular quantum register expression.

Do this conversion by running this awk program using awk -f prob6.awk, then (when it waits for your input) entering your student ID number. You will see the quantum register expression appear as output.

(a) Copy this quantum register expression (which will be a member of QUANT) and enter it as the first line in the text file prob6.txt.

Append the string “Feynman”, out of respect for the originator of quantum computing.

(b) Run your parser on your expression from (a), and report the result of evaluating it by appending the output to the file prob6.txt.

The answer to (a) should be the first line of your file prob6.txt. Your answer to (b) should occupy the remaining nine lines. The file should therefore have ten lines altogether. You can use wc prob6.txt to verify this.

For example, if your ID is 12345678, then your ten-line file prob6.txt should look like this:

(X (x) Z (x) I) * (CNOT (x) Z) * (X (x) Z (x) I) * (k0 (x) k0 (x) k0)

3-qubit register, 8-element vector:

0.000000

  0.000000

 -1.000000

  0.000000

  0.000000

  0.000000

  0.000000

  0.000000

5

Turing machines

Now refer to the description of Pauli matrices and the Pauli product word simplification function on page 21.

   Problem 7. [8 marks]

Build, in Tuatara, a Turing machine that computes the Pauli product word simplification func- tion, and save the Turing machine as a file prob7.tm.

Context-Free Languages

Now refer to the description of Walks on page 22.

Let SAW be the language of strings over the alphabet {N,S,E,W} that represent self-avoiding walks.

   Problem 8. [8 marks]

Prove or disprove: The language SAW is context-free.

Be sure to mention the Cocke-Younger-Kasami algorithm (but there is no need to demonstrate it).

Your submission can be typed or hand-written, but it must be in PDF format and saved as a file prob8.pdf.

6

Lex, Yacc and the PLUS-TIMES-POWER language

In this part of the Assignment, you will use the lexical analyser generator lex, initially by itself, and then with the parser generator yacc1.

Some useful references on Lex and Yacc:

• T. Niemann, Lex & Yacc Tutorial, http://epaperpress.com/lexandyacc/

• Doug Brown, John Levine, and Tony Mason, lex and yacc (2nd edn.), O’Reilly, 2012. • the lex and yacc manpages.

We will illustrate the use of these programs with a language PLUS-TIMES-POWER based on simple arithmetic expressions involving nonnegative integers, using just addition, multiplication and powers. Then you will use lex and yacc on some languages related to quantum computing.

PLUS-TIMES-POWER

The language PLUS-TIMES-POWER consists of expressions involving addition, multiplication and powers of nonnegative integers, without any parentheses (except for those required by the function Power). Example expressions include:

5+8, 8+5, 3+5∗2, 13+8∗4+Power(2,Power(3,2)), Power(1,3)+Power(5,3)+Power(3,3), Power(999,0), 0+99∗0+1, 2014, 10∗14+74+10∗13∗73, 2∗3∗5∗7∗11∗13∗17∗19.

In these expressions, integers are written in unsigned decimal, with no leading zeros or decimal point (so 2014, 86, 10, 7, and 0 are ok, but +2014, −2014, 86.0, A, 007, and 00 are not).

For lexical analysis, we treat every nonnegative integer as a lexeme for the token NUMBER.

Lex

An input file to lex is, by convention, given a name ending in .l. Such a file has three parts: • definitions,

• rules,

• C code.

These are separated by double-percent, %%. Comments begin with /* and end with */. Any comments are ignored when lex is run on the file.

You will find an input file, plus-times-power.l, among the files for this Assignment. Study its structure now, identifying the three sections and noticing that various pieces of code have been commented out. Those pieces of code are not needed yet, but some will be needed later.

We focus mainly on the Rules section, in the middle of the file. It consists of a series of statements of the form

pattern { action }

where the pattern is a regular expression and the action consists of instructions, written in C, specifying what to do with text that matches the pattern.2 In our file, each pattern represents a set of possible lexemes which we wish to identify. These are:

1actually, Linux includes more modern implementations of these programs called flex and bison.

2This may seem reminiscent of awk, but note that: the pattern is not delimited by slashes, /.../, as in awk; the action code is in C, whereas in awk the actions are specified in awk’s own language, which has similarities with C but is not the same; and the action pertains only to the text that matches the pattern, whereas in awk the action pertains to the entire line in which the matching text is found.

7

• a decimal representation of a nonnegative integer, represented as described above;

– This is taken to be an instance of the token NUMBER (i.e., a lexeme for that token).

• the specific string Power, which is taken to be an instance of the token POWER. • certain specific characters: +, *, (, ), and comma;

• the newline character;

• white space, being any sequence of spaces and tabs.

Note that all matching in lex is case-sensitive.

Our action is, in most cases, to print a message saying what token and lexeme have been found.

For white space, we take no action at all. A character that cannot be matched by any pattern yields an error message.

If you run lex on the file plus-times-power.l, then lex generates the C program lex.yy.c.3 This is the source code for the lexical analyser. You compile it using a C compiler such as cc.

For this assignment we use flex, a more modern variant of lex. We generate the lexical analyser as follows.

$ flex plus-times-power.l $ cc lex.yy.c

By default, cc puts the executable program in a file usually called a.out4 but sometimes called a.exe. This can be executed in the usual way, by just entering ./a.out at the command line. If you prefer to give the executable program another name, such as plus-times-power-lex, then you can tell this to the compiler using the -o option: cc lex.yy.c -o plus-times-power-lex.

When you run the program, it will initially wait for you to input a line of text to analyse. Do so, pressing Return at the end of the line. Then the lexical analyser will print, to standard output, messages showing how it has analysed your input. The printing of these messages is done by the printf statements from the file plus-times-power.l. Note how it skips over white space, and only reports on the lexemes and tokens.

$ ./a.out

13+8 * 4 + Power(2,Power Token: NUMBER; Lexeme: 13 Token and Lexeme: +

Token: NUMBER; Lexeme: 8 Token and Lexeme: *

Token: NUMBER; Lexeme: 4 Token and Lexeme: +

Token: POWER; Lexeme: Power Token and Lexeme: (

Token: NUMBER; Lexeme: 2 Token and Lexeme: ,

Token: POWER; Lexeme: Power Token and Lexeme: (

Token: NUMBER; Lexeme: 3 Token and Lexeme: ,

Token: NUMBER; Lexeme: 2 Token and Lexeme: )

Token and Lexeme: )

Token and Lexeme: <newline>

(3,2 ))

Try running this program with some input expressions of your own. You can keep entering new expressions on new lines, and enter Control-D to stop when you are finished.

3The C program will have this same name, lex.yy.c, regardless of the name you gave to the lex input file. 4a.out is short for assembler output.

8

Yacc

We now turn to parsing, using yacc.

Consider the following grammar for PLUS-TIMES-POWER.

S −→ E

E −→ I

E −→ POWER(E,E) E −→ E∗E

E −→ E+E

I −→ NUMBER

In this grammar, the non-terminals are S, E and I. Treat NUMBER and POWER as just single tokens, and hence single terminal symbols in this grammar.

We now generate a parser for this grammar, which will also evaluate the expressions, with +, ∗ interpreted as the usual integer arithmetic operations and Power(. . . ,. . . ) interpreted as raising its first argument to the power of its second argument.

To generate this parser, you need two files, prob1.l (for lex) and plus-times-power.y (for yacc):

• Change into your problem1 subdirectory and do the following steps in that directory.

• Copy plus-times-power.l to a new file prob1.l, and then modify prob1.l as follows:

– in the Definitions section, uncomment the statement #include "y.tab.h";

– in the Rules section, in each action:

∗ uncomment the statements of the form · yylval.str = ...;

· yylval.num = ...;

· return TOKENNAME;

· return *yytext;

· yyerror...

∗ Comment out the printf statements. These may still be handy if debugging is

needed, so don’t delete them altogether, but the lexical analyser’s main role now is to report the tokens and lexemes to the parser, not to the user.

– in the C code section, comment out the function main(), which in this case occupies four lines at the end of the file.

• plus-times-power.y, the input file for yacc, is provided for you. You don’t need to modify this yet.

An input file for yacc is, by convention, given a name ending in .y, and has three parts, very loosely analogous to the three parts of a lex file but very different in their details and functionality:

• Declarations, • Rules,

• Programs.

These are separated by double-percent, %%. Comments begin with /* and end with */.

Peruse the provided file plus-times-power.y, identify its main components, and pay particular

attention to the following, since you will need to modify some of them later.

9

• in the Declarations section:

– lines like

            int printMatrix(Matrix x);

            Matrix identity();

.

            Register kroneckerProductReg(Register v, Register w);

which are declarations of functions (but they are defined later, in the Programs section);5

– declarations of the tokens to be used:

            %token <num> NUMBER

            %token <str> POWER

– some specifications that certain operations are left-associative (which helps determine the order in which operations are applied and can help resolve conflicts and ambiguities):

            %left ’+’

            %left ’*’

– declarations of the nonterminal symbols to be used (which don’t need to start with an upper-case letter):

            %type <iValue> start

            %type <iValue> line

            %type <iValue> expr

            %type <iValue> int

– nomination of which nonterminal is the Start symbol: %start start

• in the Rules section, a list of grammar rules in Backus-Naur Form (BNF), except that the colon “:” is used instead of →, and there must be a semicolon at the end of each rule. Rules with a common left-hand-side may be written in the usual compact form, by listing their right-hand-sides separated by vertical bars, and one semicolon at the very end. The terminals may be token names, in which case they must be declared in the Declarations section and also used in the lex file, or single characters enclosed in forward-quote symbols. Each rule has an action, enclosed in braces {...}. A rule for a Start symbol may print output, but most other rules will have an action of the form $$ = .... The special variable $$ represents the value to be returned for that rule, and in effect specifies how that rule is to be interpreted for evaluating the expression. The variables $1, $2, . . . refer to the values of the first, second, . . . symbols in the right-hand side of the rule.

• in the Programs section, various functions, written in C, that your parsers will be able to use. You do not need to modify these functions, and indeed should not try to do so unless you are an experienced C programmer and know exactly what you are doing! Most of these functions are not used yet; some will only be used later, in Problem 4.

After constructing the new lex file prob1.l as above, the parser can be generated by:

$ yacc -d plus-times-power.y $ flex prob1.l

$ cc lex.yy.c y.tab.c -lm

The executable program, which is now a parser for PLUS-TIMES-POWER, is again named a.out by default, and will replace any other program of that name that is sitting in the same directory.

5These functions for computing with quantum expressions are not needed by plus-times-power.y, but you will need them later, when you make a modified version of plus-times-power.y to parse quantum expressions.

10

$ ./a.out

13+8 * 4 + Power(2,Power

557

13+8*4+Power(2,Power(3,2))

557 Power(1,3)+Power(5,3)+Power(3,3) 153

1+2+3+4+5+6+7+8+9+10

55

10*9*8*7*6*5*4*3*2*1

3628800

Power(999,0)

1

Control-D

(3,2 ))

Run it with some input expressions of your own. You can keep entering new expressions on new lines, as above, and enter Control-D to stop when you are finished.

11

Quantum circuits, registers and the language QUANT Introduction

Roughly speaking, a quantum computer is a computer that is able to use certain capabilities based on quantum physics in addition to the usual (“classical”) capabilities that computers have.

The idea to use quantum physics for computation arose in the 1980s with work by the physicists Richard Feynman and David Deutsch. Interest increased considerably in the 1990s when Peter Shor gave an efficient quantum algorithm for integer factorisation. It had been assumed that integer factorisation was difficult; a fast factorisation algorithm could be used to break the RSA public-key cryptosystem. RSA was the first public-key cryptosystem to be published and is still the most widely used, underpinning the security of a large proportion of modern electronic communications.6. Since then, many quantum algorithms have appeared, some improving considerably on the best classical algorithms. But, to have any impact in practice, they will have to be implemented on actual quantum computers and applied to large inputs.

Several dozen quantum computers have been built. Many of these are experimental, while some have been used for highly specialised applications. But they are nowhere near powerful enough or robust enough to be useful on a large scale. Practical quantum computing still faces huge technical challenges including adequately protecting the delicate computations from being perturbed by the surrounding environment. In spite of this, there is considerable optimism about their future, and a widespread belief that, in time, their effect will be revolutionary (as well as some scepticism about this). Although they cannot yet be used to break RSA, the threat they pose has been taken very seriously by cryptographers, whose work has led to the development of new quantum- resistant cryptosystems: https://www.nist.gov/news-events/news/2022/07/nist-announces- first-four-quantum-resistant-cryptographic-algorithms.

For a recent review of the field’s current progress and prospects, see [1]. Mathematically, the heart of a quantum computer has three parts:

• a register that stores information, and in fact can store multiple data items simultaneously, in a superposition, although these data items cannot be accessed in standard classical ways;

• a quantum circuit expression, in which certain basic components (called gates) are combined in order to produce a transformation that is applied to the register to produce another register;

• measurement, in which some part of a register is measured (i.e., read), but the result is de- termined probabilistically by the entire contents of the register, and the act of measurement reduces the amount of information held in the register.

In this assignment, we just consider registers and quantum circuit expressions, and in fact we only consider restricted types of these. Nonetheless, our registers and expressions are sufficient, in prin- ciple, to represent the pre-measurement parts of quantum computations arbitrarily accurately. We define these concepts now.

A register is a real 2n-dimensional vector of unit length. Examples of registers include:

n = 0 :

? 1 ?

n = 0 :

 1/2  −1/2 

? −1 ?

n = 1 :

? 0.6? −0.8

n=2: −1/2 

n=3:

 −0.4  

1/2

 0.2  −0.2   0 . 4 

−0.4

6Shor also gave an efficient quantum algorithm for another number-theoretic problem called discrete log. A fast

discrete log algorithm would break the Diffie-Hellman key-exchange scheme, another important cryptographic tool.

 0.6

 0.2

 −0.2 

12

There are two particular registers with n = 1 that we use repeatedly:

Some concrete examples:

Let I be the usual 2 × 2 identity matrix,

Define H by

traditional our name name

|0⟩ k0 |1⟩ k1

vector

?1? 0

?0? 1

To define quantum circuit expressions, we need two different ways of combining matrices: ordi- nary matrix multiplication, and another operation called Kronecker product which is probably new to you. We discuss these in turn.

Ordinarily, multiplying two matrices A and B is only defined if the number of columns of A equals the number of rows of B. In this assignment, we introduce a new error matrix whose sole role is to indicate that an error has been made, at some stage in a calculation, due to trying to multiply incompatible matrices. It has no rows, columns or entries, and we regard it as having n = −1. Once an error matrix appears in a calculation, you cannot get rid of it: the result of any subsequent calculation with it will again be the error matrix. With this little “hack”, we can allow any two matrices to be multiplied together; we just have to keep in mind the possibility of producing the error matrix and having it “swamp” the remainder of our current calculation.

We now define the Kronecker product.

Let A = (aij)r×c be an r×c matrix, with r rows and c columns, whose i,j-entry is aij. Similarly, let B = (bkl)s×d be an s×d matrix, with s rows and d columns, whose k,l-entry is bkl. Then the Kronecker product A ⊗ B is the rs × cd matrix, with rs rows and cd columns, formed by multiplying each entry of A by a copy of B:

 a11B a12B ··· a1cB 

 a21B a22B ··· a2cB  A⊗B =  . . .. . 

.... ar1B ar2B · · · arcB

It can be shown that the entry in row (i−1)s+k and column (j −1)d+l of A⊗B is aikbjl (where 1 ≤ i ≤ r, 1 ≤ j ≤ c, 1 ≤ k ≤ s, 1 ≤ l ≤ d). For example, if both A and B are 2 × 2 matrices, with

then

21



A⊗B= 

22

a11 b11 a11 b21 a21 b11 a21 b21

21 22

a12 b12  a12b22 .

?a11 a12 ? ?b11 b12 ? A=aa, B=bb,

a11 b12 a11 b22 a21 b12 a21 b22

a12 b11 a12 b21 a22 b11 a22 b21

a22 b12 a22 b22



?1 0? I=01.

(1)

(2)

√1 √1 H=22.

√1 −√1  22

13

Then

11  1 1 I⊗H=√2 −√2 0 0, H⊗I=0√2 0 √2.(3)

11 11 0 0√2 √2 √2 0−√2 0

 0 0 √1 −√1   0 √1 0 −√1  2222

The Kronecker product can also be applied to our vectors, which are, after all, just matrices with only one column:

0 0

0 1 k0⊗k1= 1, k1⊗k0= 0.

 

00

We see from these examples that Kronecker product is not commutative in general.

Note that the Kronecker product is always defined, regardless of the dimensions of the matrices. Quantum gates

We use a small set of fundamental matrices, called quantum gates, to help build our expressions. The quantum gates we use are:

?? √1√1 ?? ?? I=10,H=22,X=01,Z=10,

1000 I⊗I =  0 1 0 0 ,

 0 0 1 0  0001

H⊗H =

1111 2222

1 1 1 1  2 −2 2 −2 ,

  1 1 1 1   2 2−2−2

12−12−12 21

√1 0 √1 0

01

√1 −√1 22

10 0−1

√1 √1 0 0 2222

 1 0 0 0   0 1 0 0 

10000000 01000000  0 0 1 0 0 0 0 0   0 0 0 1 0 0 0 0 

TOF =  0 0 0 0 1 0 0 0 . 0 0 1 0  0 0 0 0 0 1 0 0   0 0 0 0 0 0 0 1 

CNOT =  0 0 0 1 , 

00000010

This set of gates is sufficient to build a quantum circuit to approximate any quantum computation arbitrarily closely. In fact, even the two-gate set {H, TOF} is sufficient for that.

H is known as the Hadamard gate, and X and Z are the Pauli-X and Pauli-Z gates. CNOT is the controlled-not gate and TOF is the Toffoli gate.

14

Languages for quantum expressions

Quantum circuit expressions are defined inductively as follows.

• Each of I, H, X, Z, CNOT and TOF is a quantum circuit expression.

• If Q is a quantum circuit expression, then so is (Q).

• If P and Q are quantum circuit expressions, then so is P ∗ Q. (This represents ordinary matrix multiplication.)

• If P and Q are quantum circuit expressions, then so is P ⊗ Q. (This represents Kronecker product.)

This inductive definition can be used as the starting point for writing a Context-Free Grammar for these expressions.

Quantum register expressions are defined inductively as follows.

• Each of k0 and k1 is a quantum register expression.

• If R is a quantum register expression, then so is (R).

• If R and S are quantum register expressions, then so is R ⊗ S.

• If Q is a quantum circuit expression and R is a quantum register expression, then Q ∗ R is a quantum register expression.

This inductive definition can also be used as the starting point for writing a Context-Free Grammar.

The languages QCIRC, QREG and QUANT

We define three languages to describe the types of quantum expressions we are working with.

• QCIRC is the language, over the ten-symbol alphabet {I, H, X, Z, CNOT, TOF, *, ⊗, (, ) }, of valid quantum circuit expressions.

• QREG is the language, over the twelve-symbol alphabet {I, H, X, Z, CNOT, TOF, k0, k1, *, ⊗, (, ) }, of valid quantum register expressions.

• QUANT is their union: QUANT = QCIRC ∪ QREG.

When representing members of these languages in text, we replace ⊗ by the three-letter string (x), which is intended to be as close as we can get, with keyboard characters, to a cross in a circle! (Note that it uses lower-case x.) Always remember that it is our text representation of the Kronecker product symbol ⊗; it is not an expression x enclosed in parentheses, and it is not an argument x being supplied to some function! In this assignment, we only use the lower-case letter x in this way, enclosed in one pair of parentheses in order to represent ⊗.

In lexical analysis, we treat (x) as the sole lexeme associated with the token KRONECKERPROD. We also treat k0 and k1 as the sole lexemes associated with tokens KET0 and KET1, respectively. This follows a widespread convention that token names are upper-case.

I, H, X, Z, CNOT, TOF are tokens representing the names of the matrices we use as quantum gates. Each is also the sole lexeme for its token.

The following table gives some members of QUANT. For each, we indicate in the right column whether it belongs to QCIRC or QREG.

15

quantum string evaluates

comments

QCIRC: ✓ QREG: ✗

This is a 2 × 2 identity matrix and is a valid quantum circuit expression. But it’s not a vector, so is not a quantum register expression.

QCIRC: ✓ QREG: ✗

This is also a valid quantum circuit ex- pression, but is not a vector.

expression

I

H ⊗ I

k0⊗k1

H ∗ k0

(H ∗k0)⊗(H ∗k1)

(H ⊗H)∗(k0⊗k1)