summaryrefslogtreecommitdiffhomepage
AgeCommit message (Collapse)Author
2020-10-19Version bumpJose Antonio Ortega Ruiz
2020-10-19First fully functional GTK3Jose Antonio Ortega Ruiz
2020-10-19Current line and breakpoint iconsJose Antonio Ortega Ruiz
2020-10-19Gimme back my fonts (deprecated)Jose Antonio Ortega Ruiz
2020-10-19Stock icon for quit appJose Antonio Ortega Ruiz
2020-10-19attach/detach buttonsJose Antonio Ortega Ruiz
2020-10-18mixgtk_widget_factory_get_by_nameJose Antonio Ortega Ruiz
2020-10-18Show/hide toolbarsJose Antonio Ortega Ruiz
2020-10-18Toolbars visible againJose Antonio Ortega Ruiz
2020-10-18gtk-builder-tool simplifyJose Antonio Ortega Ruiz
2020-10-18Use g_error_freeJose Antonio Ortega Ruiz
2020-10-18gtk_widget_reparent deprecationJose Antonio Ortega Ruiz
2020-10-18G_INLINE_FUNC deprecatedJose Antonio Ortega Ruiz
2020-10-18Work in progressJose Antonio Ortega Ruiz
2020-10-18Mirgration to GTK+3: widget lookup fixesJose Antonio Ortega Ruiz
2020-10-18Mirgration to GTK+3: seemingly safe changesJose Antonio Ortega Ruiz
2020-10-18mixal-mode.el synchronised with emacs'sJose Antonio Ortega Ruiz
2020-10-16Doc versions updatesJose Antonio Ortega Ruiz
2020-10-15TypoJose Antonio Ortega Ruiz
2020-10-15Support for Guile 3.x1.2.11Jose Antonio Ortega Ruiz
2020-10-15NEWS updatedJose Antonio Ortega Ruiz
2020-10-15Documentation typo (fixes #59239)Jose Antonio Ortega Ruiz
2019-04-09Change vm->address_list from GSList to GQueueJose Antonio Ortega Ruiz
The current emulator uses an unbounded linked list for tracking the memory locations our program has traveled through. On a 64 bit system, this requires 16 bytes of data for every instruction a MIX program performs. For small programs that are light on computation cycles, this does not cause a noticeable issue. For programs that execute hundreds of millions of instructions, this causes the memory footprint of the virtual machine to explode. I have attached an example MIXAL program that will cause the VM to grow to over 3 GB of memory usage when run. To run the sample, compile coin-opt.mixal (attached), run it in mixvm, and enter 499 at the prompt. Or use the following steps. This patch changes all the appropriate references to GQueue references and also caps the backtrace at 1000, which can be changed in the mixlib/mix_vm.h header. I feel like 1000 is a reasonable limit for the vast majority of debugging needs. Most people are looking back at the most recent 100 instructions or so. You can get the original behavior (unlimited tracing) back by setting the MIX_MAXTRACE to -1, albeit with a slightly higher memory cost (24 bytes per instruction). Or you can turn it off entirely by setting it to 0. Using a queue doesn't change the logic of the program in any significant way, and it allows programs to run for an extended period of time without consuming all the memory on the machine and slowing down to a crawl. -Kevin Brunelle
2019-04-09GTK Console input no longer overruns bufferJose Antonio Ortega Ruiz
Patch by Kevin Brunelle The console input in gmixvm will only read 70 characters, but the outer loop used 70 (the characters) instead of 14 (the number of words). This caused the VM to read past the end of the buffer and write 56 words of junk into the emulator.
2019-04-09Support IOC commands for disk/drum devicesJose Antonio Ortega Ruiz
Thanks to Kevin Brunelle There is a minor fix included with regards to tape devices. The test was failing if M == 0, when it should fail when M != 0. NOTICE: This patch changes the behavior of the VM and changes the function parameters for the ioc_ function. Documentation changes are included. Permits the following: LDX BLKNUM IOC 0(8) OUT ADDR(8) Write block from ADDR into disk[BLKNUM] IOC 0(8) IN ADDR(8) Read block from disk[BLKNUM] into ADDR ... BLKNUM CON 45000 Example possible block on disk I was having an issue writing a block to a drive and then reading back the same block. Because it is impossible to move the SEEK_CUR pointer backwards on a disk device, there was no way for a program to read back a block that it wrote to a disk without restarting or fiddling with ~/.mdk/disk?.dev files and symbolic links. I have added a function parameter to the ioc_ function and used it to pass the value of rX to ioc_. This permits us to use IOC commands to move the read/write head on a disk/drum device. I believe that this conforms to the potential meaning of Knuth's description of IOC for disk/drum devices. I have put in tests to verify that rX is positive and M = 0. I have updated the documentation to reflect this new behavior. This makes disks much more usable. Note: I won't be offended if this patch is rejected because it changed the behavior of the VM. I think it fits the spirit and enhances the functionality in a way that some might find useful. I wanted it for something I was working on, and I felt others might want the same. The thing with the paper-tape should be fixed, though.
2019-03-20NEWS and version bumpJose Antonio Ortega Ruiz
2019-03-20Fix: correctly rewind tapeJose Antonio Ortega Ruiz
According to the specification, if M < 0, the tape is skipped backwards M blocks, or to the beginning of the tape, whichever comes first. In the implementation, we don't check to verify that we aren't seeking past the beginning of the file. This causes fseek(3) to fail, and it leaves us at the position we were at. Diagnosis and fix by Kevin Brunelle.
2019-03-19NEWS updatesJose Antonio Ortega Ruiz
2019-03-19Fix: allow access to last mem cell in devices (#9773)Jose Antonio Ortega Ruiz
Author: Kevin Brunelle
2019-03-11Obsolete string-to-int removed in favour of string-to-numberJose Antonio Ortega Ruiz
Thanks to Thomas Matecki. Fixes #bug 55877 and makes mixvm, Philip King's child, work again!
2019-01-08Version 1.2.101.2.10Jose Antonio Ortega Ruiz
2019-01-08NEWS for 1.2.10Jose Antonio Ortega Ruiz
2019-01-08Fix for mixasm infinite loop on invalid F-specs (bug #32452)Jose Antonio Ortega Ruiz
Thanks to Sascha Wilde.
2019-01-08Fix for bug #43634: keep sign of rA for ADD/SUB yielding 0Jose Antonio Ortega Ruiz
2019-01-08Fix for bug #47208: correctly store immediate constantsJose Antonio Ortega Ruiz
We were taking only the first 3 bits of the index byte in a the word representing immediate constants, so that, for instance, =262143=, representing 00 00 63 63 63, was stored as 00 00 07 63 63.
2019-01-08Flex generation fix (invalid noreject removed)Jose Antonio Ortega Ruiz
2019-01-07Flex by-products added to CLEANFILESJose Antonio Ortega Ruiz
2019-01-07Looking for guile 2.2 during configurationJose Antonio Ortega Ruiz
2015-12-23Version upgraded to 1.2.91.2.9Jose Antonio Ortega Ruiz
2015-11-16NEWS updateJose Antonio Ortega Ruiz
2015-11-16Documentation fixes by Joshua DaviesJose Antonio Ortega Ruiz
2015-03-03Modify texinfo documentationlitvin
2015-03-03Add missed instructions: SLB,SRB,JAE,JAO,JXE,JXO (from volume 2, section 4.5.2)litvin
2014-08-04Including autogen.sh in distribution tarball1.2.8jao
2014-08-04THANKS updated for 1.2.8jao
2014-08-03NEWS updated for 1.2.8jao
2014-08-03Apparently tautological comparisons fixed (bug #42871)jao
2014-08-03Whitespacejao
2014-08-02Fix for compilation in darwin (bug #42818)jao
2014-05-21Avoiding format strings security warnings (cf. #8467)Jose Antonio Ortega Ruiz