3 ms·

> Whenever this function is called, make sure there is enough free memory ... Lisp? Forth? Smalltalk? And that's just off the top of my head. But really, a

by spc476 10y ago

> Whenever this function is called, make sure there is enough free memory ... Lisp? Forth? Smalltalk? And that's just off the top of my head. But really, an operating system with a virtual memory system will handle that mess for you. > analzye this library and include a logically simplified version that only needs to address these cases I think SynthesisOS (an operating system, not a programming language) could pull that off to a degree (the kernel was JIT'ed and therefore, customized system calls could be developed). > if variables A and B ever both change as a result of the same function call ... I wouldn't be surprised if GDB couldn't do this. I know it can watch both reads and writes, so this should be possible. How easy is a different answer. And you know, the best way to get to the future is to invent the future ...

vidarh 10y ago
> I think SynthesisOS (an operating system, not a programming language) could pull that off to a degree (the kernel was JIT'ed and therefore, customized system calls could be developed). I keep meaning to spend more time looking at SynthesisOS [1] - it deserves more attention. The JIT'ing as a means to speed up system functions by specialising them could be useful all over the place, and I think one of the most important contributions is that it doesn't need to be done everywhere - you can specialise JIT'ing of very small portions of hot codepaths and get a lot of the benefit at very low cost. For those not familiar with Synthesis, chapter 3 of [1] is a good place for a quick summary of the techniques used. Section 3.3.1 gives concrete examples. (The old Amiga user in me is very pleased Synthesis used M68k - makes the assembler examples very nostalgic...) [1] Synthesis: An Efficient Implementation of Fundamental Operating System Services Alexia Massalin - http://valerieaurora.org/synthesis/SynthesisOS/ http://valerieaurora.org/synthesis/SynthesisOS/
- renox 10y ago
  If I remember well it had no memory protection, incompatible by design so..

by spc476 10y ago

vidarh 10y ago

> I think SynthesisOS (an operating system, not a programming language) could pull that off to a degree (the kernel was JIT'ed and therefore, customized system calls could be developed). I keep meaning to spend more time looking at SynthesisOS [1] - it deserves more attention. The JIT'ing as a means to speed up system functions by specialising them could be useful all over the place, and I think one of the most important contributions is that it doesn't need to be done everywhere - you can specialise JIT'ing of very small portions of hot codepaths and get a lot of the benefit at very low cost. For those not familiar with Synthesis, chapter 3 of [1] is a good place for a quick summary of the techniques used. Section 3.3.1 gives concrete examples. (The old Amiga user in me is very pleased Synthesis used M68k - makes the assembler examples very nostalgic...) [1] Synthesis: An Efficient Implementation of Fundamental Operating System Services Alexia Massalin - http://valerieaurora.org/synthesis/SynthesisOS/ http://valerieaurora.org/synthesis/SynthesisOS/

renox 10y ago
If I remember well it had no memory protection, incompatible by design so..