Re: How do you do this?



Alex McDonald wrote:
Yes, I do. Th word DEMO is Forth and is in common to all; the rest is
not comparing like with like. You're comparing the comms latency of
whatever connects your chips, and the sleep to wake capabilities of
your chip, the nature, size and complexity of the supporting
infrastructure... It's a function of the platform on which the Forth
runs.

Yes. Exactly. That and whatever software is needed on top of
whatever hardware there is there is. All computing takes a combination
of hardware and software.

As you have correctly deduced my question comes down to what
software and hardware combination would you use to do this on
your computer and what would the software look like? So in addition
to the code you need to desribe the computer and interface used
even if it is just a wire.

In my case; a Forth on a single PC that communicates courtesy of a
heavyweight OS written in C over a LAN to other PCs. However, it does
have a damn fine spell-checker.

So in that case, simply answer for how YOUR code would look like
and what it would do if one of those 'other PCs' also had your code
running on it. Sort of like if you owned two of them yourself and
connected them up however you like.

Of course, I'm guessing; but in your case, it would be a SEAforth chip
running Forth that sits centimetres from its neighbour with bandwidth I
can only dream of, and no spell checker.

Yeah, well I didn't ask you about 'my case' I will tell you about that,
you don't need to tell me about my case. I asked you about your
case of how do you do this? Hence the thread.

In your defence, I'll note that message passing benchmarks are such a
difficult area that SPEC doesn't have one, but is looking for
contributions. See http://www.spec.org/mpi/; this is "Your opportunity
to be a RECOGNIZED EXPERT in the HPC Community".

Defense? I created a thread when I asked a simple question and
got a few answers so far. Defense? Am I under attack here? ;-)

But thanks again. Yeah, I have studied the mpi, message passing
interface stuff, and it did have an influence on the ROM BIOS and
forthlet library and tools. Thanks anyway but I am not seeking
recognition in the HPC community, I guess it would be nice if
people liked seeing a sort of micro-mpi.

And thanks for the opinion that the problem is one that is simply
too big a nut for the SPEC world to crack.

.



Relevant Pages

  • Re: 32 bit FORTH ??? Different tack! Jona
    ... CPUs available. ... I/O for your particular target hardware, and your done, as far as ... If you write a "UNIX" OS, ... AMD chips, INTEL chips, ...
    (comp.lang.forth)
  • Re: What does (v) in menus stand for?
    ... chips rode piggy back, one chip on top of another and sharing the same ... and the correct fix was to cut it. ... problems getting this through my management, as I was a ... I managed, though a friend in the hardware department, to get ...
    (alt.usage.english)
  • Re: How to make Windows XP last for the next seven years
    ... having to spend the money to upgrade or get new hardware. ... down to removing and replacing chips on boards. ... capacitor that was leaking badly on the motherboard. ...
    (soc.retirement)
  • Re: Inspiron 1525 Hardware
    ... The 1.2.73 commit also added support for the 88E8048 and the 88E8070. ... The Linux folks refer to these chips as "FE+". ... CSet revisions worth looking at (clicking the revision string will take ... CSet 1.6247.96.1 -- fix for recv status hardware bug in FE+ chips ...
    (freebsd-stable)
  • Re: A whopping 50 percent... ???
    ... > It takes a certina amount of money to build a computer. ... I know that RISC chips had much higher clock rates. ... There were vax chips that performed well. ... comparing the older VAX ones with the newer RISC ones. ...
    (comp.os.vms)