Index of /history.dcs.ed.ac.uk/archive/languages/imp77-tmp/gtoal/icode2ast

      Name                    Last modified      Size  Description
Parent Directory - pass1-flat.c 2026-05-15 13:22 105K icode-summary.txt 2026-08-20 23:58 14K genimp.h 2026-09-19 13:30 292 icode2ast_data.h 2026-09-19 13:30 908 imptoc.h 2026-09-19 13:30 1.8K impsig.h 2026-09-19 13:30 3.3K tables.h 2026-09-19 13:30 20K systemf.c 2026-09-19 13:30 1.6K pathopen.h 2026-09-19 13:30 162 pathopen.c 2026-09-19 13:30 6.4K impsup-signals.c 2026-09-19 13:30 11K pass2.icd 2026-09-19 13:30 252K strcompat.c 2026-09-19 22:50 2.4K DOWNLOAD.sh 2026-09-26 10:42 4.0K stack.h 2026-09-26 10:44 899 pass2.c.html 2026-09-27 00:48 405K pass2.imp.html 2026-09-27 10:15 284K cygprofile-elf.c 2026-09-29 00:00 5.0K perms.h 2026-09-29 15:06 48K icode2ast_data.c 2026-10-02 20:19 13K genc.h 2026-10-03 00:25 288 genimp.c 2026-10-07 22:56 71K README.txt 2026-10-10 20:42 1.0K filter.h 2026-10-10 20:47 1.1K README-CURRENT-BUGS.txt 2026-10-11 00:31 3.9K errorf.c 2026-10-13 12:08 3.6K errorf.h 2026-10-13 12:08 461 filter.c 2026-10-13 12:08 28K decode-arch.c 2026-10-16 12:53 12K TEST.log 2026-10-18 11:58 25M test.tar 2026-10-18 12:00 134M decode-arch.sh 2026-10-19 01:42 16K icode2ast.c 2026-10-19 20:14 48K TEST.sh 2026-10-19 20:28 13K showicode.h 2026-10-20 12:22 359 icode2ast.h 2026-10-20 12:24 28K pass2test/ 2026-10-20 14:17 - showicode.c 2026-10-20 14:32 32K stack.c 2026-10-20 14:33 63K Makefile 2026-10-20 15:29 5.2K genc.c 2026-10-20 16:23 143K main.c 2026-10-20 19:45 9.3K TEST.log.html 2026-10-21 21:54 549K test/ 2026-10-21 21:54 -
Out of 615 regression tests only 17 now fail to compile.  The majority of the failures are in large complex programs - mostly imp compilers (though pass1's seem to compile OK)

Anything using generic %name is not implemented yet.

Anything that requires a dopevector (mainly 2D array parameters) isn't implemented yet

There are a couple of actual code bugs that cause the compiler to crash, that I haven't started to track down yet.

The state of the new library, backtrace, signal, etc etc is anyone's guess.  I won't be putting much effort into those until after it compiles all the sources I can throw at it.

With all those caveats, I do think I'm close to saying you might try it on some simpler test programs.  Maybe not today but soon.  (I need to simplify how you would download and build it in a test subdirectory before I ask you to try it out.)

It's not going to be at the "let's throw tough examples at it as see if they work" stage, it'll be more like the "Wow, it does actually seem to run 'Hello World'" stage :-)