1. PLD CPUs
On 16 Oct 2000, at 0:18, David Cuny wrote:
> R. W. D. wrote:
<snip>
> > I assume that some hardware guy somewhere is
> > slapping together microprocessor to execute Java
> > bytecode. If Euphoria could emit this bytecode, it
> > would have a jump on other languages when such
> > a microprocessor becomes available.
>
> Actually, a number of chips (like Transmeta's) go a step further and allow
> you define your own opcodes. So you can tell the CPU to behave like an x86,
> and run PC programs, and then a 68000 and run old Mac code, execute Java
> code natively, or even (bleah) run .NET.
For how these cpus work:
http://www.vcc.com/intro1.html
For a list of the CPUs based on PLDs:
http://www.io.com/~guccione/HW_list.html
Some listed are relatively old in the puter terms, and designed for research,
not speed
or mass production puters. It was a home pc being a gui and watching over these
PLDs on a separate board that broke the encryption scheme the feds were pushing
a
couple yrs ago, and did it in *hours*, not thousands of yrs. And since you can
stack
them sideways, you can easily build a motherbd that can munge a .bmp in one
clock
tick, or pick 1000's of 64Kbyte wildcard patterns out of real-time streaming
audio or
video.
Kat,
still believing that if you can't do it in one 1ns "clock cycle", you are doing
something
wrong.
PS, i was just thinking that the cpu i designed was going to pull 100amps at
5vdc
*worstcase*, but looking at it in power/work ratio, it still beat any cpu i can
buy now.
Same with these PLDs,, if built right, one command may spike awful power
demands,
but the next 100 commands may not pull enough power to allow a pentium to even
power up and idle.
