| From: | Jim Peters |
| Date: | 11 Sep 2000 at 09:34:44 |
| Subject: | Re: Subject: Re: [RE: AMIOPEN: has anyone run SPEC benchmark using VP?] |
On Fri, Oct 17, 2036 at 11:45:42PM -0700, James Russell wrote:
> I DO know that VP code looks for a native tool FIRST (they are marked as 0,
> where non-native is 1 and above). I don't know how far this goes, so
> concievably you could use entirely native toolsets. If you were only ever
> going to use one processor, it would then make sense to do this(?).
>
> Is this the case, anyone? Can you go entirely native with VP code? Should
> you?
If an optimising VP->native code compiler can do a better job than the
built-in VP (even if just by 10%), then why not ? Leave it running
overnight, generating native tools from each of the VP ones, and see
the speed-up next morning. This is possible, right ? If so, it might
be a nice project for someone somewhere down the line, to squeeze the
last drops of power out of their particular processor. But I think
the idea is that mostly there's no point - the VP is designed to be
fast enough to save you from the temptation to code natively (and lose
your portability and `code immortality' by breaking compatibility with
the Amiga virtual machine).
Jim