You're reading from Build Your Own Programming Language A programmer's guide to designing compilers, interpreters, and DSLs for modern computing problems

Product type Paperback

Published in Jan 2024

Publisher Packt

ISBN-13 9781804618028

Length 556 pages

Edition 2nd Edition

Languages

Java

Tools

Java EE

Concepts

Programming Language

Author (1):

Clinton L. Jeffery

View More author details

Table of Contents (27) Chapters

Preface

1. Section I: Programming Language Frontends

2. Why Build Another Programming Language? FREE CHAPTER

3. Programming Language Design

4. Scanning Source Code

5. Parsing

6. Syntax Trees

7. Section II: Syntax Tree Traversals

8. Symbol Tables

9. Checking Base Types

10. Checking Types on Arrays, Method Calls, and Structure Accesses

11. Intermediate Code Generation

12. Syntax Coloring in an IDE

13. Section III: Code Generation and Runtime Systems

14. Preprocessors and Transpilers

15. Bytecode Interpreters

16. Generating Bytecode

17. Native Code Generation

18. Implementing Operators and Built-In Functions

19. Domain Control Structures

20. Garbage Collection

21. Final Thoughts

22. Section IV: Appendix

23. Answers

24. Other Books You May Enjoy

25. Index

Appendix: Unicon Essentials

Generating x64 output

As with many traditional compilers, the native code for Jzero will be produced by carrying out the following steps. First, we will write out a linked list of x64 objects in a human-readable assembler language with the .s extension. We then invoke the GNU assembler to turn that into a binary object file format with the .o extension. An executable is constructed by invoking a linker, which combines a set of .o files specified by the user with a set of .o files containing runtime library code, and data referenced from the generated code. This section presents each of these steps, starting with producing the assembler code.

Writing the x64 code in assembly language format

This section provides a brief description of the x64 assembler format as supported by the GNU assembler, which uses AT&T syntax. Instructions and pseudo-instructions occur on a line by themselves with a tab (or eight spaces) of indentation on the left. Labels are an exception to this...