Construction of LL(1) Parsing Table
Last Updated :
11 Jul, 2025
Parsing is an essential part of computer science, especially in compilers and interpreters. From the various parsing techniques, LL(1) parsing is best. It uses a predictive, top-down approach. This allows efficient parsing without backtracking. This article will explore parsing and LL(1) parsing. It will cover its structure, how to build an LL(1) parsing table and its benefits.
What is LL(1) Parsing?
Here the 1st L represents that the scanning of the Input will be done from the Left to Right manner and the second L shows that in this parsing technique, we are going to use the Left most Derivation Tree. And finally, the 1 represents the number of look-ahead, which means how many symbols you will see when you want to make a decision.

Conditions for an LL(1) Grammar
To construct a working LL(1) parsing table, a grammar must satisfy these conditions:
- No Left Recursion: Avoid recursive definitions like A -> A + b.
- Unambiguous Grammar: Ensure each string can be derived in only one way.
- Left Factoring: Make the grammar deterministic, so the parser can proceed without guessing.
Algorithm to Construct LL(1) Parsing Table
Step 1: First check all the essential conditions mentioned above and go to step 2.
Step 2: Calculate First() and Follow() for all non-terminals.
- First(): If there is a variable, and from that variable, if we try to drive all the strings then the beginning Terminal Symbol is called the First.
- Follow(): What is the Terminal Symbol which follows a variable in the process of derivation.
Step 3: For each production A --> α. (A tends to alpha)
- Find First(α) and for each terminal in First(α), make entry A --> α in the table.
- If First(α) contains ε (epsilon) as terminal, then find the Follow(A) and for each terminal in Follow(A), make entry A --> ε in the table.
- If the First(α) contains ε and Follow(A) contains $ as terminal, then make entry A --> ε in the table for the $.
To construct the parsing table, we have two functions:
In the table, rows will contain the Non-Terminals and the column will contain the Terminal Symbols. All the Null Productions of the Grammars will go under the Follow elements and the remaining productions will lie under the elements of the First set.
Now, let's understand with an example.
Example 1: Consider the Grammar:
E --> TE'
E' --> +TE' | ε
T --> FT'
T' --> *FT' | ε
F --> id | (E)
*ε denotes epsilon
Step 1: The grammar satisfies all properties in step 1.
Step 2: Calculate first() and follow().
Find their First and Follow sets:
| First | Follow |
---|
E --> TE' | { id, ( } | { $, ) } |
E' --> +TE'/ ε | { +, ε } | { $, ) } |
T --> FT' | { id, ( } | { +, $, ) } |
T' --> *FT'/ ε | { *, ε } | { +, $, ) } |
F --> id/(E) | { id, ( } | { *, +, $, ) } |
Step 3: Make a parser table.
Now, the LL(1) Parsing Table is:
| id | + | * | ( | ) | $ |
---|
E | E --> TE' | | | E --> TE' | | |
E' | | E' --> +TE' | | | E' --> ε | E' --> ε |
T | T --> FT' | | | T --> FT' | | |
T' | | T' --> ε | T' --> *FT' | | T' --> ε | T' --> ε |
F | F --> id | | | F --> (E) | | |
As you can see that all the null productions are put under the Follow set of that symbol and all the remaining productions lie under the First of that symbol.
Note: Every grammar is not feasible for LL(1) Parsing table. It may be possible that one cell may contain more than one production.
Let's see an example.
Example 2: Consider the Grammar
S --> A | a
A --> a
Step 1: The grammar does not satisfy all properties in step 1, as the grammar is ambiguous. Still, let's try to make the parser table and see what happens
Step 2: Calculating first() and follow()
Find their First and Follow sets:
| First | Follow |
---|
S --> A/a | { a } | { $ } |
A -->a | { a } | { $ } |
Step 3: Make a parser table.
Parsing Table:
| a | $ |
---|
S | S --> A, S --> a | |
A | A --> a | |
Here, we can see that there are two productions in the same cell. Hence, this grammar is not feasible for LL(1) Parser.
Trick - Above grammar is ambiguous grammar. So the grammar does not satisfy the essential conditions. So we can say that this grammar is not feasible for LL(1) Parser even without making the parse table.
Example 3: Consider the Grammar
S -> (L) | a
L -> SL'
L' -> )SL' | ε
Step1: The grammar satisfies all properties in step 1
Step 2: Calculating first() and follow()
| First | Follow |
---|
S | ( , a | $, ) |
L | ( , a | ) |
L' | ), ε | ) |
Step 3: Making a parser table
Parsing Table:
| ( | ) | a | $ |
---|
S | S -> (L) | | S -> a | |
L | L -> SL' | | L -> SL' | |
L' |
| L'->(SL' L'->ε | | |
Here, we can see that there are two productions in the same cell. Hence, this grammar is not feasible for LL(1) Parser. Although the grammar satisfies all the essential conditions in step 1, it is still not feasible for LL(1) Parser. We saw in example 2 that we must have these essential conditions and in example 3 we saw that those conditions are insufficient to be a LL(1) parser.
Advantages of Construction of LL(1) Parsing Table
- Clear Decision-Making: With an LL(1) parsing table, the parser can decide what to do by looking at just one symbol ahead. This makes it easy to choose the right rule without confusion or guessing.
- Fast Parsing: Since there’s no need to go back and forth or guess the next step, LL(1) parsing is quick and efficient. This is useful for applications like compilers where speed is important.
- Easy to Spot Errors: The table helps identify errors right away. If the current symbol doesn’t match any rule in the table, the parser knows there’s an error and can handle it immediately.
- Simple to Implement: Once the table is set up, the parsing process is straightforward. You just follow the instructions in the table, making it easier to build and maintain.
- Good for Predictive Parsing: LL(1) parsing is often called “predictive parsing” because the table lets you predict the next steps based on the input. This makes it reliable for parsing programming languages and structured data.
Similar Reads
Introduction of Compiler Design A compiler is software that translates or converts a program written in a high-level language (Source Language) into a low-level language (Machine Language or Assembly Language). Compiler design is the process of developing a compiler.The development of compilers is closely tied to the evolution of
9 min read
Compiler Design Basics
Introduction of Compiler DesignA compiler is software that translates or converts a program written in a high-level language (Source Language) into a low-level language (Machine Language or Assembly Language). Compiler design is the process of developing a compiler.The development of compilers is closely tied to the evolution of
9 min read
Compiler construction toolsThe compiler writer can use some specialized tools that help in implementing various phases of a compiler. These tools assist in the creation of an entire compiler or its parts. Some commonly used compiler construction tools include: Parser Generator - It produces syntax analyzers (parsers) from the
4 min read
Phases of a CompilerA compiler is a software tool that converts high-level programming code into machine code that a computer can understand and execute. It acts as a bridge between human-readable code and machine-level instructions, enabling efficient program execution. The process of compilation is divided into six p
10 min read
Symbol Table in CompilerEvery compiler uses a symbol table to track all variables, functions, and identifiers in a program. It stores information such as the name, type, scope, and memory location of each identifier. Built during the early stages of compilation, the symbol table supports error checking, scope management, a
8 min read
Error Handling in Compiler DesignDuring the process of language translation, the compiler can encounter errors. While the compiler might not always know the exact cause of the error, it can detect and analyze the visible problems. The main purpose of error handling is to assist the programmer by pointing out issues in their code. E
5 min read
Language Processors: Assembler, Compiler and InterpreterComputer programs are generally written in high-level languages (like C++, Python, and Java). A language processor, or language translator, is a computer program that convert source code from one programming language to another language or to machine code (also known as object code). They also find
5 min read
Generation of Programming LanguagesProgramming languages have evolved significantly over time, moving from fundamental machine-specific code to complex languages that are simpler to write and understand. Each new generation of programming languages has improved, allowing developers to create more efficient, human-readable, and adapta
6 min read
Lexical Analysis
Introduction of Lexical AnalysisLexical analysis, also known as scanning is the first phase of a compiler which involves reading the source program character by character from left to right and organizing them into tokens. Tokens are meaningful sequences of characters. There are usually only a small number of tokens for a programm
6 min read
Flex (Fast Lexical Analyzer Generator)Flex (Fast Lexical Analyzer Generator), or simply Flex, is a tool for generating lexical analyzers scanners or lexers. Written by Vern Paxson in C, circa 1987, Flex is designed to produce lexical analyzers that is faster than the original Lex program. Today it is often used along with Berkeley Yacc
7 min read
Introduction of Finite AutomataFinite automata are abstract machines used to recognize patterns in input sequences, forming the basis for understanding regular languages in computer science. They consist of states, transitions, and input symbols, processing each symbol step-by-step. If the machine ends in an accepting state after
4 min read
Classification of Context Free GrammarsA Context-Free Grammar (CFG) is a formal rule system used to describe the syntax of programming languages in compiler design. It provides a set of production rules that specify how symbols (terminals and non-terminals) can be combined to form valid sentences in the language. CFGs are important in th
4 min read
Ambiguous GrammarContext-Free Grammars (CFGs) is a way to describe the structure of a language, such as the rules for building sentences in a language or programming code. These rules help define how different symbols can be combined to create valid strings (sequences of symbols).CFGs can be divided into two types b
7 min read
Syntax Analysis & Parsers
Syntax Directed Translation & Intermediate Code Generation
Syntax Directed Translation in Compiler DesignSyntax-Directed Translation (SDT) is a method used in compiler design to convert source code into another form while analyzing its structure. It integrates syntax analysis (parsing) with semantic rules to produce intermediate code, machine code, or optimized instructions.In SDT, each grammar rule is
8 min read
S - Attributed and L - Attributed SDTs in Syntax Directed TranslationIn Syntax-Directed Translation (SDT), the rules are those that are used to describe how the semantic information flows from one node to the other during the parsing phase. SDTs are derived from context-free grammars where referring semantic actions are connected to grammar productions. Such action c
4 min read
Parse Tree and Syntax TreeParse Tree and Syntax tree are tree structures that represent the structure of a given input according to a formal grammar. They play an important role in understanding and verifying whether an input string aligns with the language defined by a grammar. These terms are often used interchangeably but
4 min read
Intermediate Code Generation in Compiler DesignIn the analysis-synthesis model of a compiler, the front end of a compiler translates a source program into an independent intermediate code, then the back end of the compiler uses this intermediate code to generate the target code (which can be understood by the machine). The benefits of using mach
6 min read
Issues in the design of a code generatorA code generator is a crucial part of a compiler that converts the intermediate representation of source code into machine-readable instructions. Its main task is to produce the correct and efficient code that can be executed by a computer. The design of the code generator should ensure that it is e
7 min read
Three address code in CompilerTAC is an intermediate representation of three-address code utilized by compilers to ease the process of code generation. Complex expressions are, therefore, decomposed into simple steps comprising, at most, three addresses: two operands and one result using this code. The results from TAC are alway
6 min read
Data flow analysis in CompilerData flow is analysis that determines the information regarding the definition and use of data in program. With the help of this analysis, optimization can be done. In general, its process in which values are computed using data flow analysis. The data flow property represents information that can b
6 min read
Code Optimization & Runtime Environments
Practice Questions