Portage of Oberon system to stm32f429i-disco board
Version 6 released!
- Oberon MSP430 compiler:
Work in progress: parser and generator are under testing. Instruction generator and disassembler are tested OK. See osmp/README.md for information about MSP430 specific extensions. - Minor fixes on OM4 compiler.
- Introduction of one time initialized global variables in OM4 and OMSP compilers:
Global variables whose type is followed by an hypen sign are now read only, except in the initialization block of the module. - Kernel.Coalesce fix
- StackTrace fix (requires recompilation of modules)
- Improved mouse management
QWERTY keyboard can be activated by middle clicking on the text "OM4P.Compile InputM4Qwerty.Mod ~"
displayed in yellow in the middle of the System.Tool window. Restart the system to load the updated Input module.
Changes in oberon 07 compiler:
Registers usage control in procedures
Cortex M4 microcontrollers save automatically a set of registers on stack when servicing an interruption.
If an Oberon exception handler contains too complicated expressions, there is a risk that a non saved register is used.
To prevent that case to happen, I introduced a new notation ^n after the PROCEDURE keyword:
PROCEDURE^3 handler;
BEGIN ....
END handler;
With this information, the compiler can check that no more than n registers are used. The save/restoration instructions are automatically generated according to the declared number of used registers.
Unsafe local variables marking
This Oberon compiler allow allocation of unitialized pointers on stack.
Those pointers are not checked at runtime, so they are not safe until they are properly intialized.
I made a change in the compiler to allow detection of the declaration of local variables containing pointers. The developer must check the code to be sure that no bad use is made with these variables.
For example, assume that a Files.Rider is declared as a local variable. Using of the "file" member (eg. via Files.Base) is unsafe until the rider has been initialized with Files.Set.
When the developer has determined that the code usage of the local variable is safe, he or she must mark the variable with an exclamation mark (!) in its declaration.
Oberon runs now on the STM32F429I-DISCO base board:
Hardware side:
