Search found 103 matches

by gray
Tue Jan 18, 2022 1:08 pm
Forum: Astrobe for FPGA RISC5
Topic: RISC5 Oberon Compiler Source Code
Replies: 1
Views: 7863

Re: RISC5 Oberon Compiler Source Code

Wow. Thanks! Also for CPIde.
by gray
Sat Jan 15, 2022 8:01 am
Forum: Astrobe for FPGA RISC5
Topic: Spurious Imports
Replies: 5
Views: 12034

Re: Spurious Imports

Thanks! The indirectly imported modules do count as regards the max allowed 15 imported modules, which we can check in the BL opcode of an external procedure call, where the module number is encoded in a 4 bit value (hence the restriction of 15, zero is not a valid module number for BL instructions)...
by gray
Sat Jan 01, 2022 9:53 am
Forum: Astrobe for FPGA RISC5
Topic: Spurious Imports
Replies: 5
Views: 12034

Re: Spurious Imports

OK, thanks, I have read up. Does the Astrobe compiler more or less work like the Project Oberon one in that area? In particular the import and export of symbols (reading and writing of symbol files, ORB. Import and ORB.Export) and creating object files (ORG.Close)? The way the symbol table is built ...
by gray
Thu Dec 30, 2021 11:39 am
Forum: Astrobe for FPGA RISC5
Topic: Spurious Imports
Replies: 5
Views: 12034

Spurious Imports

In the process of debugging an inexplicable error during the system start-up sequence I started to look into 'rsc' files (yes, I know), namely the list of imported modules. I have realised that the list of imports in the 'rsc' files sometimes contains additional modules that are not in the IMPORT li...
by gray
Thu Dec 30, 2021 10:56 am
Forum: Bug Reports
Topic: System.Exception in RISC5 Compiler
Replies: 0
Views: 15500

System.Exception in RISC5 Compiler

Test case: MODULE M1; CONST OK := M2.OK; END M1. Note the missing IMPORT statement. With the v8.0 compiler: OR Compiler 17.10.2021 compiling M1 2 14 Error: = ? 2 18 Error: undef System.Exception: CASE-trap: selector = 54 at ORP.ORP.factor(Item& x) at ORP.ORP.term(Item& x) at ORP.ORP.SimpleExpression...
by gray
Thu Oct 28, 2021 5:21 am
Forum: Astrobe for FPGA RISC5
Topic: System.Date (v8.0)
Replies: 1
Views: 7762

Re: System.Date (v8.0)

Checking for the correctness of the date and time actually set is also useful as we actually can set the clock even with incorrect parameters. Here are two example cases with incorrect parameters where the clock gets set nonetheless. Typos happen. :( System.Date 28 10 n21 10 20 30 System.Date 28 10 ...
by gray
Mon Oct 25, 2021 9:19 am
Forum: Astrobe for FPGA RISC5
Topic: System.Date (v8.0)
Replies: 1
Views: 7762

System.Date (v8.0)

The new System.Date procedure in v8.0: PROCEDURE Date*; (* ... *) BEGIN (* ... *) IF S.class = Texts.Int THEN (*set clock*) (* ... *) IF (day >= 1) & (day <= 31) & (mo >= 1) & (mo <= 12) & (yr >= 0) & (yr <= 63) THEN dt := ((((yr*16 + mo)*32 + day)*32 + hr)*64 + min)*64 + sec; Kernel.SetClock(dt) EN...
by gray
Mon Oct 25, 2021 8:31 am
Forum: Astrobe for FPGA RISC5
Topic: ASSERT & Error.Mod (version 8.0)
Replies: 1
Views: 7682

ASSERT & Error.Mod (version 8.0)

Astrobe for RISC v8.0 provides a new module Error.Mod. It is used, for example, in Math.Mod: PROCEDURE Sqrt*(x: REAL): REAL; (* ... *) BEGIN ASSERT(x >= 0.0, Error.input); (* ... *) END Sqrt; That is, to provide an error code for ASSERT via a second parameter (which could be any integer value, does ...
by gray
Wed Jun 02, 2021 4:28 am
Forum: Astrobe for FPGA RISC5
Topic: Self-unloading With Modules.Free?
Replies: 2
Views: 10561

Re: Self-unloading With Modules.Free?

Thanks for your information and insights. Your general words of caution are useful in any case, as in case "self-freeing" would not work, the unloading could easily be delegated to an extended loader process/task that would free the first program before loading the subsequent one. My current design ...
by gray
Tue Jun 01, 2021 9:23 am
Forum: Astrobe for FPGA RISC5
Topic: Self-unloading With Modules.Free?
Replies: 2
Views: 10561

Self-unloading With Modules.Free?

Is there any reason why, or a situation when, this would not work? MODULE M; IMPORT Modules, Oberon; PROCEDURE Run*; BEGIN Modules.Free("M"); Oberon.Collect(0) END Run; END M. That is, a module unloading itself. The reasoning here is that Modules.Free just sets the module name to the empty string, a...