Parsing #1. Leonidas Fegaras. CSE 5317/4305 L3: Parsing #1 1

Similar documents
Chapter 3. Parsing #1

CSE 3302 Programming Languages Lecture 2: Syntax

8 Parsing. Parsing. Top Down Parsing Methods. Parsing complexity. Top down vs. bottom up parsing. Top down vs. bottom up parsing

Downloaded from Page 1. LR Parsing

CSCI312 Principles of Programming Languages

Parsing III. CS434 Lecture 8 Spring 2005 Department of Computer Science University of Alabama Joel Jones

Parsing. Note by Baris Aktemur: Our slides are adapted from Cooper and Torczon s slides that they prepared for COMP 412 at Rice.

CS1622. Today. A Recursive Descent Parser. Preliminaries. Lecture 9 Parsing (4)

Top down vs. bottom up parsing

Syntax Analysis, III Comp 412

Top-Down Parsing and Intro to Bottom-Up Parsing. Lecture 7

Syntactic Analysis. Top-Down Parsing

shift-reduce parsing

Building a Parser III. CS164 3:30-5:00 TT 10 Evans. Prof. Bodik CS 164 Lecture 6 1

Parsing II Top-down parsing. Comp 412

Top-Down Parsing and Intro to Bottom-Up Parsing. Lecture 7

Parsing III. (Top-down parsing: recursive descent & LL(1) )

Compilers. Predictive Parsing. Alex Aiken

Note that for recursive descent to work, if A ::= B1 B2 is a grammar rule we need First k (B1) disjoint from First k (B2).

Parsing. Roadmap. > Context-free grammars > Derivations and precedence > Top-down parsing > Left-recursion > Look-ahead > Table-driven parsing

Bottom-Up Parsing. Parser Generation. LR Parsing. Constructing LR Parser

Lexical and Syntax Analysis. Top-Down Parsing

Parser Generation. Bottom-Up Parsing. Constructing LR Parser. LR Parsing. Construct parse tree bottom-up --- from leaves to the root

Abstract Syntax. Leonidas Fegaras. CSE 5317/4305 L5: Abstract Syntax 1

Types of parsing. CMSC 430 Lecture 4, Page 1

Syntax Analysis, III Comp 412

Lexical and Syntax Analysis

Compilers. Yannis Smaragdakis, U. Athens (original slides by Sam

Parsing Part II (Top-down parsing, left-recursion removal)

Introduction to Parsing. Comp 412

Administrativia. WA1 due on Thu PA2 in a week. Building a Parser III. Slides on the web site. CS164 3:30-5:00 TT 10 Evans.

Context-Free Grammar. Concepts Introduced in Chapter 2. Parse Trees. Example Grammar and Derivation

Ambiguity, Precedence, Associativity & Top-Down Parsing. Lecture 9-10

LL(k) Parsing. Predictive Parsers. LL(k) Parser Structure. Sample Parse Table. LL(1) Parsing Algorithm. Push RHS in Reverse Order 10/17/2012

CS 406/534 Compiler Construction Parsing Part I

3. Parsing. Oscar Nierstrasz

Defining syntax using CFGs

Abstract Syntax Trees & Top-Down Parsing

Abstract Syntax Trees & Top-Down Parsing

Abstract Syntax Trees & Top-Down Parsing

Monday, September 13, Parsers

Parsers. Xiaokang Qiu Purdue University. August 31, 2018 ECE 468

4 (c) parsing. Parsing. Top down vs. bo5om up parsing

Parsing Part II. (Ambiguity, Top-down parsing, Left-recursion Removal)

Wednesday, September 9, 15. Parsers

CA Compiler Construction

Parsers. What is a parser. Languages. Agenda. Terminology. Languages. A parser has two jobs:

Syntax Analysis. Martin Sulzmann. Martin Sulzmann Syntax Analysis 1 / 38

CS415 Compilers. Syntax Analysis. These slides are based on slides copyrighted by Keith Cooper, Ken Kennedy & Linda Torczon at Rice University

CSE431 Translation of Computer Languages

Syntax Analysis Part I

Wednesday, August 31, Parsers

([1-9] 1[0-2]):[0-5][0-9](AM PM)? What does the above match? Matches clock time, may or may not be told if it is AM or PM.

Introduction to Bottom-Up Parsing

1 Introduction. 2 Recursive descent parsing. Predicative parsing. Computer Language Implementation Lecture Note 3 February 4, 2004

COMP 181. Prelude. Next step. Parsing. Study of parsing. Specifying syntax with a grammar

Syntax-Directed Translation. Lecture 14

CS 314 Principles of Programming Languages

Derivations vs Parses. Example. Parse Tree. Ambiguity. Different Parse Trees. Context Free Grammars 9/18/2012

Context-Free Grammars

CSE 401 Midterm Exam Sample Solution 2/11/15

Front End. Hwansoo Han

Context-free grammars (CFG s)

Ambiguity. Grammar E E + E E * E ( E ) int. The string int * int + int has two parse trees. * int

A programming language requires two major definitions A simple one pass compiler

Extra Credit Question

Section A. A grammar that produces more than one parse tree for some sentences is said to be ambiguous.

Review main idea syntax-directed evaluation and translation. Recall syntax-directed interpretation in recursive descent parsers

LL Parsing: A piece of cake after LR

Review of CFGs and Parsing II Bottom-up Parsers. Lecture 5. Review slides 1

CMSC 330: Organization of Programming Languages

COP 3402 Systems Software Syntax Analysis (Parser)

CMSC 330: Organization of Programming Languages

Prelude COMP 181 Tufts University Computer Science Last time Grammar issues Key structure meaning Tufts University Computer Science

CS2210: Compiler Construction Syntax Analysis Syntax Analysis

It parses an input string of tokens by tracing out the steps in a leftmost derivation.

CMSC 330: Organization of Programming Languages. Architecture of Compilers, Interpreters

COMP-421 Compiler Design. Presented by Dr Ioanna Dionysiou

The procedure attempts to "match" the right hand side of some production for a nonterminal.

Revisit the example. Transformed DFA 10/1/16 A B C D E. Start

COP4020 Programming Languages. Syntax Prof. Robert van Engelen

Part 3. Syntax analysis. Syntax analysis 96

COP 3402 Systems Software Top Down Parsing (Recursive Descent)

Table-Driven Top-Down Parsers

Syntax Analysis Check syntax and construct abstract syntax tree

Recursive Descent Parsers

Outline. The strategy: shift-reduce parsing. Introduction to Bottom-Up Parsing. A key concept: handles

Parsing Algorithms. Parsing: continued. Top Down Parsing. Predictive Parser. David Notkin Autumn 2008

Syntax Analysis, V Bottom-up Parsing & The Magic of Handles Comp 412

LANGUAGE PROCESSORS. Introduction to Language processor:

CS 4120 Introduction to Compilers

LL(1) Grammars. Example. Recursive Descent Parsers. S A a {b,d,a} A B D {b, d, a} B b { b } B λ {d, a} D d { d } D λ { a }

Syntax Analysis/Parsing. Context-free grammars (CFG s) Context-free grammars vs. Regular Expressions. BNF description of PL/0 syntax

COP4020 Programming Languages. Syntax Prof. Robert van Engelen

Building A Recursive Descent Parser. Example: CSX-Lite. match terminals, and calling parsing procedures to match nonterminals.

Parsing. Handle, viable prefix, items, closures, goto s LR(k): SLR(1), LR(1), LALR(1)

Syntax/semantics. Program <> program execution Compiler/interpreter Syntax Grammars Syntax diagrams Automata/State Machines Scanning/Parsing

Lexical and Syntax Analysis (2)

Sometimes an ambiguous grammar can be rewritten to eliminate the ambiguity.

EDAN65: Compilers, Lecture 06 A LR parsing. Görel Hedin Revised:

Transcription:

Parsing #1 Leonidas Fegaras CSE 5317/4305 L3: Parsing #1 1

Parser source file get next character scanner get token parser AST token A parser recognizes sequences of tokens according to some grammar and generates Abstract Syntax Trees (ASTs) A context-free grammar (CFG) has a finite set of terminals (tokens) a finite set of nonterminals from which one is the start symbol and a finite set of productions of the form: A ::= X1 X2... Xn where A is a nonterminal and each Xi is either a terminal or nonterminal symbol CSE 5317/4305 L3: Parsing #1 2

Example Expressions: E ::= E + T E - T T T ::= T * F T / F F F ::= num id Nonterminals: E T F Start symbol: E Terminals: + - * / id num Example: x+2*y... or equivalently: E ::= E + T E ::= E - T E ::= T T ::= T * F T ::= T / F T ::= F F ::= num F ::= id CSE 5317/4305 L3: Parsing #1 3

Derivations Notation: terminals: t, s,... nonterminals: A, B,... symbol (terminal or nonterminal): X, Y,... sequence of symbols: a, b,... Given a production: A ::= X 1 X 2... X n the form aab => ax 1 X 2... X n b is called a derivation eg, using the production T ::= T * F we get T / F + 1 - x => T * F / F + 1 - x Leftmost derivation: when you always expand the leftmost nonterminal in the sequence Rightmost derivation:... rightmost nonterminal CSE 5317/4305 L3: Parsing #1 4

Top-down Parsing It starts from the start symbol of the grammar and applies derivations until the entire input string is derived Example that matches the input sequence id(x) + num(2) * id(y) E => E + T use E ::= E + T => E + T * F use T ::= T * F => T + T * F use E ::= T => T + F * F use T ::= F => T + num * F use F ::= num => F + num * F use T ::= F => id + num * F use F ::= id => id + num * id use F ::= id You may have more than one choice at each derivation step: my have multiple nonterminals in each sequence for each nonterminal in the sequence, may have many rules to choose from Wrong predictions will cause backtracking need predictive parsing that never backtracks CSE 5317/4305 L3: Parsing #1 5

Bottom-up Parsing It starts from the input string and uses derivations in the opposite directions (from right to left) until you derive the start symbol Previous example: id(x) + num(2) * id(y) <= id(x) + num(2) * F use F ::= id <= id(x) + F * F use F ::= num <= id(x) + T * F use T ::= F <= id(x) + T use T ::= T * F <= F + T use F ::= id <= T + T use T ::= F <= E + T use E ::= T <= E use E ::= E + T At each derivation step, need to recognize a handle (the sequence of symbols that matches the right-hand-side of a production) CSE 5317/4305 L3: Parsing #1 6

Parse Tree Given the derivations used in the top-down/bottom-up parsing of an input sequence, a parse tree has the start symbol as the root E the terminals of the input sequence as leafs for each production A ::= X 1 X 2... X n used in a derivation, a node A with children X 1 X 2... X n E T T T F F F id(x) + num(2) * id(y) E => E + T => E + T * F => T + T * F => T + F * F => T + num * F => F + num * F => id + num * F => id + num * id CSE 5317/4305 L3: Parsing #1 7

Playing with Associativity What about this grammar? E ::= T + E T - E T T ::= F * T F / T F F ::= num id Right associative Now x+y+z is equivalent to x+(y+z) E T E F T E F T F id(x) + id(y) + id(z) CSE 5317/4305 L3: Parsing #1 8

Ambiguous Grammars What about this grammar? E ::= E + E E - E E * E E / E num id E E E E E id(x) * id(y) + id(z) E E E E E id(x) * id(y) + id(z) Operators + - * / have the same precedence! It is ambiguous: has more than one parse tree for the same input sequence (depending which derivations are applied each time) CSE 5317/4305 L3: Parsing #1 9

Predictive Parsing The goal is to construct a top-down parser that never backtracks Always leftmost derivations left recursion is bad! We must transform a grammar in two ways: eliminate left recursion perform left factoring These rules eliminate most common causes for backtracking although they do not guarantee a completely backtrack-free parsing CSE 5317/4305 L3: Parsing #1 10

Left Recursion Elimination For example, the grammar A ::= A a b recognizes the regular expression ba*. But a top-down parser may have hard time to decide which rule to use Need to get rid of left recursion: A ::= b A' A' ::= a A' ie, A' parses the RE a*. The second rule is recursive, but not left recursive CSE 5317/4305 L3: Parsing #1 11

Left Recursion Elimination (cont.) For each nonterminal X, we partition the productions for X into two groups: one that contains the left recursive productions the other with the rest That is: X ::= X a 1... X ::= X a n X ::= b 1... X ::= b m where a and b are symbol sequences. Then we eliminate the left recursion by rewriting these rules into: X ::= b 1 X' X' ::= a 1 X'...... X' ::= a X ::= b m X' n X' X' ::= CSE 5317/4305 L3: Parsing #1 12

Example E ::= E + T E - T T T ::= T * F T / F F F ::= num id E ::= T E' E' ::= + T E' - T E' T ::= F T' T' ::= * F T' / F T' F ::= num id CSE 5317/4305 L3: Parsing #1 13

Example A grammar that recognizes regular expressions: R ::= R R R bar R R * ( R ) char After left recursion elimination: R ::= ( R ) R' char R' R' ::= R R' bar R R' * R' CSE 5317/4305 L3: Parsing #1 14

Left Factoring Factors out common prefixes: X ::= a b 1... X ::= a b n becomes: X ::= a X' X' ::= b 1... X' ::= b n Example: E ::= T + E T - E T E ::= T E' E' ::= + E - E CSE 5317/4305 L3: Parsing #1 15

Recursive Descent Parsing E ::= T E' E' ::= + T E' - T E' T ::= F T' T' ::= * F T' / F T' F ::= num id static void E () { T(); Eprime(); } static void Eprime () { if (current_token == PLUS) { read_next_token(); T(); Eprime(); } else if (current_token == MINUS) { read_next_token(); T(); Eprime(); }; } static void T () { F(); Tprime(); } static void Tprime() { if (current_token == TIMES) { read_next_token(); F(); Tprime(); } else if (current_token == DIV) { read_next_token(); F(); Tprime(); }; } static void F () { if (current_token == NUM current_token == ID) read_next_token(); else error(); } CSE 5317/4305 L3: Parsing #1 16

Predictive Parsing Using a Table The symbol sequence from a derivation is stored in a stack (first symbol on top) if the top of the stack is a terminal, it should match the current token from the input if the top of the stack is a nonterminal X and the current input token is t, we get a rule for the parse table: M[X,t] the rule is used as a derivation to replace X in the stack with the right-hand symbols push(s); read_next_token(); repeat X = pop(); if (X is a terminal or '$') if (X == current_token) read_next_token(); else error(); else if (M[X,current_token] == "X ::= Y1 Y2... Yk") { push(yk);... push(y1); } else error(); until X == '$'; CSE 5317/4305 L3: Parsing #1 17

Parsing Table Example 1) E ::= T E' $ 2) E' ::= + T E' 3) - T E' 4) 5) T ::= F T' 6) T' ::= * F T' 7) / F T' 8) 9) F ::= num 10) id num id + - * / $ E 1 1 E' 2 3 4 T 5 5 T' 8 8 6 7 8 F 9 10 CSE 5317/4305 L3: Parsing #1 18

Example: Parsing x-2*y$ top Stack current_token Rule E x M[E,id] = 1 (using E ::= T E' $) $ E' T x M[T,id] = 5 (using T ::= F T') $ E' T' F x M[F,id] = 10 (using F ::= id) $ E' T' id x read_next_token $ E' T' - M[T',-] = 8 (using T' ::= ) $ E' - M[E',-] = 3 (using E' ::= - T E') $ E' T - - read_next_token $ E' T 2 M[T,num] = 5 (using T ::= F T') $ E' T' F 2 M[F,num] = 9 (using F ::= num) $ E' T' num 2 read_next_token $ E' T' * M[T',*] = 6 (using T' ::= * F T') $ E' T' F * * read_next_token $ E' T' F y M[F,id] = 10 (using F ::= id) $ E' T' id y read_next_token $ E' T' $ M[T',$] = 8 (using T' ::= ) $ E' $ M[E',$] = 4 (using E' ::= ) $ $ stop (accept) CSE 5317/4305 L3: Parsing #1 19

Constructing the Parsing Table FIRST[a] is the set of terminals t that result after a number of derivations on the symbol sequence a ie, a =>... => tb for some symbol sequence b FIRST[ta]={t} eg, FIRST[3+E]={3} FIRST[X]=FIRST[a 1 ] FIRST[a n ] for each production X ::= a i FIRST[Xa]=FIRST[X] but if X has an empty derivation then FIRST[Xa]=FIRST[X] FIRST[a] FOLLOW[X] is the set of all terminals that follow X in any legal derivation find all productions Z ::= a X b in which X appears at the RHS; then FIRST[b] must be included in FOLLOW[X] if b has an empty derivation, FOLLOW[Z] must be included in FOLLOW[X] CSE 5317/4305 L3: Parsing #1 20

Example 1) E ::= T E' $ 2) E' ::= + T E' 3) - T E' 4) 5) T ::= F T' 6) T' ::= * F T' 7) / F T' 8) 9) F ::= num 10) id FIRST FOLLOW E {num,id} {} E' {+,-} {$} T {num,id} {+,-,$} T' {*,/} {+,-,$} F {num,id} {+,-,*,/,$} CSE 5317/4305 L3: Parsing #1 21

Constructing the Parsing Table (cont.) For each rule X ::= a do: for each t in FIRST[a], add X ::= a to M[X,t] if a can be reduced to the empty sequence, then for each t in FOLLOW[X], add X ::= a to M[X,t] 1) E ::= T E' $ 2) E' ::= + T E' 3) - T E' 4) 5) T ::= F T' 6) T' ::= * F T' 7) / F T' 8) 9) F ::= num 10) id FIRST FOLLOW E {num,id} {} E' {+,-} {$} T {num,id} {+,-,$} T' {*,/} {+,-,$} F {num,id} {+,-,*,/,$} num id + - * / $ E 1 1 E' 2 3 4 T 5 5 T' 8 8 6 7 8 F 9 10 CSE 5317/4305 L3: Parsing #1 22

Another Example G ::= S $ S ::= ( L ) a L ::= L, S S 0) G := S $ 1) S ::= ( L ) 2) S ::= a 3) L ::= S L' 4) L' ::=, S L' 5) L' ::= ( ) a, $ G 0 0 S 1 2 L 3 3 L' 5 4 CSE 5317/4305 L3: Parsing #1 23

LL(1) A grammar is called LL(1) if each element of the parsing table of the grammar has at most one production element the first L in LL(1) means that we read the input from left to right the second L means that it uses left-most derivations only the number 1 means that we need to look one token ahead from the input CSE 5317/4305 L3: Parsing #1 24