OpenEuphoria

Re: 64 bit euphoria

• Posted by Daniel Kluss <codepilot at gmail.com> Apr 22, 2005
• 464 views

Kenneth Rhodes wrote:
> 
> Robert Craig wrote:
> > 
> 
> > There is hardly any asm in the Euphoria interpreter.
> > The front-end is written in Euphoria.
> > The back-end is 99.9% C. integers would likely become 63 bits 
> > instead of 31. That could lead to some small compatibility issues,
> > e.g. 
> >   if integer(x) then ... 
> > might have a different meaning.
> > 
> > It would probably not bother many people if a 
> > simple declaration of:
> >   integer x
> > now allowed x to be 63 bits in size.
> > 
> > The use of 64-bit pointers internally by the interpreter 
> > would probably not disturb most Euphoria programs. 
> > It would just allow much larger sequences to be created.
> 
> Just how big of a performance hit would the interpreter take
> if that 1% of the front-end code was written in C?
> 
> I believe that most, if not all, of the 64 bit processors will
> run at clock speeds exceeding 2Ghz which is probably about X50
> faster than when Euphoria was first released. If the interpreter's 
> speed is not throttled drastically, it
> might be just as appealing for development and would make
> the faster translated/compiled option an even more attractive 
> purchase.
> 
> Also, it seems that hence forth the 64bit cpus will multi-core,
> so shouldn't threads be a "must" feature for the next version of
> Euphoria?

The threads should definetly be a must, real threads, not simulated threads.
Dan
> 
> 
> Ken Rhodes
> 100% Microsoft Free!
>