egorklementev / era_compiler Goto Github PK

View Code? Open in Web Editor NEW

0.0 1.0 0.0 1.52 MB

A compiler for ERA microprocessor system-level programming language.

C# 99.02% Vim Script 0.98%

era_compiler's Introduction

ERA COMPILER

This is system-level programming language compiler for processors with ERA architecture.

Basic architecture

The most abstract architecture of the compiler:

File with code -> Lexical Analyzer ->
-> Tokens -> Syntax Analyzer ->
-> Abstract Syntax Tree -> Semantic Analyzer ->
-> Annotated AST -> Generator ->
-> File with compiled code

Compiler usage

Compiler works as console appilcation.
The main command is ERACompiler.
There are several arguments available:

-h : see help
-s {filename} : specify source files to be compiled
-o {filename} : specify output files
-d {paths} : specify folders with the code to be compiled (cannot be used with -o parameter)
-p : force to create folders if they do not exist
--err : display more detailed error messages
--lex : perform tokenization only
--syn : perform tokenization and AST assembling
--sem : perform tokenization, AST assembling, and AAST assembling
--semext : same as --sem with more detailed output
--asm : full compilation with the assembly code output
--prefix : custom filename prefix for output files
--ignconf : ignore configuration file and rely only upon command-line flags

Examples of commands:
ERACompiler -h - get help message
ERACompiler -s test.txt folder1/file1.java - will compile source files to compiled_test.txt and folder1/compiled_file1.java
ERACompiler --lex -o out.a - will compile default code.era file to the out.a using only tokenization

ERA Simulator

Here is the link to the ERA Simulator GitHub repo:
https://github.com/egorklementev/era_simulator

It is aslo a Windows x64 command-line application with similar arguments and way of usage.

Vim syntax highlight

Since no one want to program in the "notepad.exe" (why not?), there is a special era.vim file that adds a support of ERA language syntax highlighting. You may find it in the ../DOCS folder. How to use Vim and its syntax highlighting, you may find in Google.

The support for VS/VSCode, Intellij IDEA, and etc. will be added later.

ATTENTION:

It is highly recommended to read example.era file which gives basic understanding of the ERA language.
example.era

Also, read documentation files in ../DOCS folder for more information about ERA language.

era_compiler's People

Contributors

Watchers

era_compiler's Issues

[8] Remove registers from routine parameters.

REASON: To make the language simpler. Debatable topic. Maybe changed later.

Dereference rule bug

REASON: The Semantic Analyzer does not parse this rule correctly.

[21] Add variable declarations to the "Statement" rule.

REASON: To allow variable declaration inside loops, "ifs", etc.

[9] Remove "label" rule

REASON: To make the language simpler. Maybe changed later.

[7] Change "type" rule.

REASON: Not all types are present, for example, pointer type or array type.

[6] Add "return" syntax rule.

See #6

[3] Return type rule

The functions should return some values and we want to know their types.

[35] Display more accurate syntax error messages

REASON: For better user experience.

[30] Change "Reference" rule to primary.

REASON: We want to get the address not only of variable but also modules (via dot notation), routine returns, etc.

Pragma declaration is seen as variable

REASON: All pragma declarations are seen as variables that should be declared.

Multiplication optimization

REASON: It is faster to use ASL with subtraction rather than just an addition a lot of times.

[23] Prioritization of operations.

REASON: Multiplication has more priority over addition. It should be fixed.

[42] Identify all declarations inside the module

REASON: Similar to #30

Fix README.md

[10] Change "asm" rule

REASON: To make code more uniform.

[32] Rearrange the "Expression" children in Semantic Analyzer

REASON: To make it easier to parse expressions in the Generator and then generate expression-related bytes.

[2] "start" & "entry" syntax rules

The purpose of these rules is not clear.

Precalculate all constant sub expressions

[14] What is "?" operator?

REASON: Do not understand the functionality of this operator.

[4] Fix "ConstDefinition" rule

REASON: To make the code rules more uniform.

[12] Context decent with the dot-notation.

REASON: We want to access structure elements or module routines using dot notation so that we have better modularity in the language.

Statements in the block should be numbered

[36] Constants can be modified

REASON: Constants cannot be modified after their definition. Should be fixed.

Implement SSA

REASON: We need it to simplify code optimizations and register allocation.

Identify all the versions of variables
Numerate all the statements
When IF block occurs (without "else"), identify all variables reassigned inside it and compute FI function based on this information
When IF block occurs (with "else"), act as previously plus identify all the variables that are used in both blocks
When FOR, WHILE, or LOOP WHILE blocks occur, act as in IF block case (without "else")

[5] Change "data" rule (remove ',')

REASON: To make code more uniform.

[38] Compiler terminates in case of a compilation error

REASON: We should not (ideally) terminate the compiler execution in case of an error. It is then hard to test it. And also if some files contain errors, we definitely want to compile the rest of them.