Re: [Ql-Users] XTC68 Status Report

2009-10-27 Thread gdgqler
On 27 Oct 2009, at 09:45, Urs Koenig (QL) wrote: If I need th software to go faster, then I re-programme in Assembler and use a QL with a fast processor. Good one. ;-) I'm still writing my stuff in SuperBASIC under QPC2/Q-emuLator on a Core2Duo (L7500/1.6Ghz) Notebook I write perhaps half i

Re: [Ql-Users] XTC68 Status Report

2009-10-27 Thread Urs Koenig (QL)
> Sorry to cause problems, but it is only what I read. No problem. I just wanted to be sure if running speed is the same no matter if compiled with C68 or XTC68. > If I need th software to go faster, then I re-programme in > Assembler and use a QL with a fast processor. Good one. ;-) I'm still wr

Re: [Ql-Users] XTC68 Status Report

2009-10-27 Thread derek stewart
Hi Urs, Sorry to cause problems, but it is only what I read. If I need th software to go faster, then I re-programme in Assembler and use a QL with a fast processor. Derek Urs Koenig (QL) wrote: UKQ> 1. Are the binaries 1:1 (file compare)? 1. Yes - except you have to recreate the QDOS file

Re: [Ql-Users] XTC68 Status Report

2009-10-27 Thread Urs Koenig (QL)
> > UKQ> 1. Are the binaries 1:1 (file compare)? > > 1. Yes - except you have to recreate the QDOS file header > > (file type and dataspace) once you get the file onto a QDOS > > volume. > If I remember right, there can be a 30% increase in speed. If the compiled binaries are 100% identical this w

Re: [Ql-Users] XTC68 Status Report

2009-10-26 Thread Derek Stewart
If I remember right, there can be a 30% increase in speed. I am not sure if this is correct, but I am sure that Prowess running faster when compiled with XTC68. Derek Adrian D. Ives wrote: Urs, As you said, to the QL community it means "Just" that one can compile QDOS-programs under Windows

Re: [Ql-Users] XTC68 Status Report

2009-10-26 Thread Adrian D. Ives
Urs, As you said, to the QL community it means "Just" that one can compile QDOS-programs under Windows. This is useful, however, for those only running emulators, because it means compilation can happen at the full speed of the native OS' CPU, rather than the (admittedly very efficient) emulated

Re: [Ql-Users] XTC68 Status Report

2009-10-26 Thread Urs Koenig (QL)
> Just to close off my original request, I have now > successfully recompiled C68 (as XTC68) under Open Watcom C > Version 1.8 and MinGW (Minimalist GNU for Windows) GCC 3.4.5. > The latter version is useful because it integrates very well > with the MinGW environment and allows MinGW Make to b

Re: [Ql-Users] XTC68 Status Report

2009-10-25 Thread P Witte
Adrian D. Ives writes: <> ToolWatcom Name MinGW Name ~~~ ~~ Assembler as68qas Compilerc68 qc Front End qcc qcc Linker qld qld Pre-Processor qcppqpp Make

Re: [Ql-Users] XTC68 Status Report

2009-10-25 Thread Adrian D. Ives
Dave, I'm very happy to do that. I think it makes a lot of sense for this to be hosted with the rest of C68. I'll zip the current stuff up and send it over to you. I've tried to retain the "multi-platform compatibility" of the original by continuing to use compile time defines to select the appro

Re: [Ql-Users] XTC68 Status Report

2009-10-25 Thread Dave Walker
...@lists.q-v-d.com [mailto:ql-users-boun...@lists.q-v-d.com] On Behalf Of Adrian D. Ives Sent: 25 October 2009 08:10 To: ql-us...@q-v-d.com Subject: [Ql-Users] XTC68 Status Report Just to close off my original request, I have now successfully recompiled C68 (as XTC68) under Open Watcom C Version 1.8 and

Re: [Ql-Users] XTC68 Status Report

2009-10-25 Thread Derek Stewart
Hi Adian, Looks like you have done a fantastic job with XTC68, I would be interested in having a look. Have you got a web site that files are made available. Derek Adrian D. Ives wrote: Just to close off my original request, I have now successfully recompiled C68 (as XTC68) under Open Watco

[Ql-Users] XTC68 Status Report

2009-10-25 Thread Adrian D. Ives
Just to close off my original request, I have now successfully recompiled C68 (as XTC68) under Open Watcom C Version 1.8 and MinGW (Minimalist GNU for Windows) GCC 3.4.5. The latter version is useful because it integrates very well with the MinGW environment and allows MinGW Make to be used to bui