Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.forth > #58537

Re: typical actual time for implementing kernel in a new architecture?

Show all headers | View raw

On 5/2/2017 2:41 PM, Stephen Pelc wrote:
> On Mon, 1 May 2017 02:24:38 -0700 (PDT), Joel Rees
> <joel.rees@gmail.com> wrote:
> 
>> For those who regularly implement kernels in new CPU architectures, about h=
>> ow long does it take on average? And how does your current expected time co=
>> mpare with your first conversion time?
> 
> The quick answer: between 3 days and 3 months. The first number is
> for an ITC Forth for a CPU you are familiar with starting from
> another Forth. The second number is for a fully optimising VFX grade
> Forth for another CPU for which you have no tools.
> 
> The long answer is that the commercial vendors don't write new
> kernels unless they have to - say the default standard changes
> significantly. MPE has written three kernels in 30+ years.
> We have however ported the VFX code generator to about 6 CPU
> architectures in 15 years. In order to do this port, you have
> to write an assembler, disassembler, code generator and some
> target code. The first VFX code generator used about 18 person-
> months. Nowadays, we would quote you for three months work -
> it just depends how much a peformance uplify of 10:1 is worth.
> 
> Stephen
> 
The current port that I'm working on will take an estimate of two to 
three weeks of man-hours spread over a couple of month, I will not be 
including and optimizer for the generated code, that task is a lot of 
effort that will get done as a separate project once I have a working 
compiler. My main goal now is portability, later the optimizer will 
become more important. This process includes learning the implementation 
language which will cause a slowdown of the whole process.

A project follow will be to implement the compiler using VFX Forth as 
the implementing language, that I estimate will be a shorter process as 
Forth is language that allows code to be written and debugged faster, 
plus the fact that some of the existing features in the VFX Forth 
compiler can be utilized to make the process faster. This will be my 
first major project in VFX Forth so there will be a learning curve also 
although not a large as with the Go Language.

-- 
Cecil - k5nwa

Back to comp.lang.forth | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

typical actual time for implementing kernel in a new architecture? Joel Rees <joel.rees@gmail.com> - 2017-05-01 02:24 -0700
  Re: typical actual time for implementing kernel in a new architecture? Lars Brinkhoff <lars.spam@nocrew.org> - 2017-05-01 17:40 +0200
    Re: typical actual time for implementing kernel in a new architecture? Ron Aaron <rambamist@gmail.com> - 2017-05-01 19:35 +0300
      Re: typical actual time for implementing kernel in a new architecture? Lars Brinkhoff <lars.spam@nocrew.org> - 2017-05-02 08:13 +0200
    Re: typical actual time for implementing kernel in a new architecture? Joel Rees <joel.rees@gmail.com> - 2017-05-01 15:17 -0700
      Re: typical actual time for implementing kernel in a new architecture? hughaguilar96@gmail.com - 2017-05-01 20:11 -0700
      Re: typical actual time for implementing kernel in a new architecture? Lars Brinkhoff <lars.spam@nocrew.org> - 2017-05-02 09:07 +0200
  Re: typical actual time for implementing kernel in a new architecture? Rod Pemberton <NeedNotReplyHere@xrsevnneqk.cem> - 2017-05-01 18:34 -0400
  Re: typical actual time for implementing kernel in a new architecture? "Elizabeth D. Rather" <erather@forth.com> - 2017-05-01 12:41 -1000
  Re: typical actual time for implementing kernel in a new architecture? hughaguilar96@gmail.com - 2017-05-01 19:33 -0700
  Re: typical actual time for implementing kernel in a new architecture? Mark Wills <markwills1970@gmail.com> - 2017-05-02 01:51 -0700
  Re: typical actual time for implementing kernel in a new architecture? minforth@arcor.de - 2017-05-02 06:17 -0700
    Re: typical actual time for implementing kernel in a new architecture? Cecil Bayona <cbayona@cbayona.com> - 2017-05-02 12:59 -0500
      Re: typical actual time for implementing kernel in a new architecture? "Elizabeth D. Rather" <erather@forth.com> - 2017-05-02 10:07 -1000
        Re: typical actual time for implementing kernel in a new architecture? Cecil Bayona <cbayona@cbayona.com> - 2017-05-02 15:39 -0500
          Re: typical actual time for implementing kernel in a new architecture? minforth@arcor.de - 2017-05-02 22:29 -0700
            Re: typical actual time for implementing kernel in a new architecture? Cecil Bayona <cbayona@cbayona.com> - 2017-05-03 01:12 -0500
              Re: typical actual time for implementing kernel in a new architecture? minforth@arcor.de - 2017-05-03 02:06 -0700
                Re: typical actual time for implementing kernel in a new architecture? Cecil Bayona <cbayona@cbayona.com> - 2017-05-03 13:52 -0500
                Re: typical actual time for implementing kernel in a new architecture? minforth@arcor.de - 2017-05-03 22:23 -0700
                Re: typical actual time for implementing kernel in a new architecture? Ilya Tarasov <ilya74.tarasov@gmail.com> - 2017-05-04 04:59 -0700
    Re: typical actual time for implementing kernel in a new architecture? Rob Sciuk <rob@controlq.com> - 2017-05-08 15:38 -0400
  Re: typical actual time for implementing kernel in a new architecture? stephen@mpeforth.com (Stephen Pelc) - 2017-05-02 19:41 +0000
    Re: typical actual time for implementing kernel in a new architecture? Cecil Bayona <cbayona@cbayona.com> - 2017-05-02 15:25 -0500

csiph-web