Earlier quoted context omitted.
Wouldn't work for all applications, tough, if I'm not mistaken, as you specifically need Silicon for imaging chips (CCD/CMOS). Or is that nonsense?
Theoretically you can make integrated circuit with any semiconductor, but I don't know if anyone has been brave enough to try it. The smallest integrated circuit is a diode, it has 1/2 transistors :). OK, a diode is not actually an integrated circuit, but if you can use a material to make a diode, you probably can use the same material to make an integrated circuit with enough money, time and ingenuity. Some of the d…
RTX2010 – Radiation-hardened stack machine microprocessor
31–40 of 61 posts
Re: RTX2010 – Radiation-hardened stack machine microprocessor
#32Earlier quoted context omitted.
Wouldn't work for all applications, tough, if I'm not mistaken, as you specifically need Silicon for imaging chips (CCD/CMOS). Or is that nonsense?
Other materials have been used for imagers. Gallium Arsenide in particular has been used for high speed, and high radiation, imaging circuits.
Re: RTX2010 – Radiation-hardened stack machine microprocessor
#33I wonder how hard it is to create a radiation hardened CPU. Is the premise that radiation can flip bits in the on-die cache and registers? would simply making those redundant be a solution? Or could a single flash of radiation invalidate all memory on the device?
If it's rad-hard, it's export-controlled in the US. See the US Munitions List, category XV, section (d), "Radiation-hardened microelectronic circuits". https://www.pmddtc.state.gov/regulations_laws/documents/offi... So mass market products aren't made radiation-hard. Rad-hard CPUs more modern than that FORTH engine exist; Atmel makes a rad-hard SPARC. But they're produced in tiny quantities and are thus very expensiv…
Re: RTX2010 – Radiation-hardened stack machine microprocessor
#34http://users.ece.cmu.edu/~koopman/stack_computers/index.html
The RTX2010 has had its own wikipedia entry too since 2008 : http://en.wikipedia.org/wiki/RTX2010
Re: RTX2010 – Radiation-hardened stack machine microprocessor
#35Earlier quoted context omitted.
Optimal register allocation is an NP-complete problem. By doing away with it, you don't need to allocate registers. How that compares on a practical level, I have no idea. But it's one of the reasons the JVM has a stack-based model and no registers: it makes writing compilers for JVM byte code a lot easier.
Interesting. I agree with your statement regarding it being an NP-complete problem, as intuitively it seems that way, but do you have a reference by chance? Thanks!
Re: RTX2010 – Radiation-hardened stack machine microprocessor
#36Earlier quoted context omitted.
Wouldn't work for all applications, tough, if I'm not mistaken, as you specifically need Silicon for imaging chips (CCD/CMOS). Or is that nonsense?
Why would you need silicon for that? Even if it were the only process we use now (which it isn't. As a simple example, Germanium-based photo diodes do exist), materials research could conceivably produce other materials that work, too. There are even more exotic examples to think of. Eyes turn light into electricity without (AFAIK) Silicon. Maybe part of that physics/chemistry can be practically used elsewhere?
Re: RTX2010 – Radiation-hardened stack machine microprocessor
#37Can someone point to resources comparing stack machines and register based machines? The RTX2010 technical documentation talks about all the advantages of a stack machine but doesn't say anything about its shortcomings.
Optimal register allocation is an NP-complete problem. By doing away with it, you don't need to allocate registers. How that compares on a practical level, I have no idea. But it's one of the reasons the JVM has a stack-based model and no registers: it makes writing compilers for JVM byte code a lot easier.
In terms of compiler writing, if you wanted to write any optimisations you'd probably want to manipulate 3-address code internally, if only because the data flow based analyses would be made easier (and then you would emit stack code in the last step).
This might be a reason why the JVM designers decided to use a stack machine, but I doubt it's an important one - they'd easily be able to get ahold of a few decent compiler writers if they needed to.
Re: RTX2010 – Radiation-hardened stack machine microprocessor
#38Another microprocessor able to execute Forth natively is the b16, from one of the original authors of Gforth. http://bernd-paysan.de/b16.html
Re: RTX2010 – Radiation-hardened stack machine microprocessor
#39Earlier quoted context omitted.
Optimal register allocation is an NP-complete problem. By doing away with it, you don't need to allocate registers. How that compares on a practical level, I have no idea. But it's one of the reasons the JVM has a stack-based model and no registers: it makes writing compilers for JVM byte code a lot easier.
This isn't quite right - we don't in general really care whether we're allocating optimally (for example, if we have 16 registers we don't care if we can potentially allocate to 10), and heuristic based approaches are practically very useful (and cheap). In terms of compiler writing, if you wanted to write any optimisations you'd probably want to manipulate 3-address code internally, if only because the data flow bas…
Re: RTX2010 – Radiation-hardened stack machine microprocessor
#40How cool - I joined Harris after grad school expressly to work on RTX architecture issues. (Previously I was a Forth developer.) Nice to see this neat-but-underappreciated architecture in the news.
>Nice to see this neat-but-underappreciated architecture in the news. It's already appreciated. Let me recall here the 'scientist' character (A&B Srugatsky) who explains the World as a huge inertial mass to the good or evil in the same. Tertium non datur it is a principle of our mind sometimes used in computers.