Drobe :: The archives
About Drobe | Contact | RSS | Twitter | Tech docs | Downloads | BBC Micro

Reply to thread

Peter has said why he did it to a number of people. Its so he can get on with the port without the constant whining of users of 13 year old machines complaining that code aimed primarily at muli-GHz x86 PCs doesn,t work fast enough on thier 200MHz StrongARMs. Frankly given the perpetual moaning on csa, I fully endorse this position.

Both GCC and Norcroft can produce code optimised for XScale scheduling but not using XScale specific instructions, or 16bit load and stores if required. When Peter has finished the port all the source will be made available under the GPL and people will be able to compile it for whatever they want, and then the pointless bleating can start all over again.

 is a RISC OS Userdruck on 1/1/07 7:27PM
[ Reply | Permalink | Report ]

Please login before posting a comment. Use the form on the right to do so or create a free account.

Search the archives

Today's featured article

  • Qercus reviewed but renewed?
    Forty months after taking out an annual subscription, Martin Hansen ponders whether or not to continue his Qercus sub
     28 comments, latest by hzn on 3/8/07 4:15PM. Published: 27 Jul 2007

  • Random article

  • Notate your music with abcMIDI

     Discuss this. Published: 28 Jan 2001

  • Useful links

    News and media:

    Top developers:
    RISCOS LtdRISC OS OpenMW SoftwareR-CompAdvantage SixVirtualAcorn

    CJE MicrosAPDLCastlea4X-AmpleLiquid SiliconWebmonster


    RISCOS.org.ukRISCOS.orgRISCOS.infoFilebaseChris Why's Acorn/RISC OS collectionNetSurf

    Non-RISC OS:
    The RegisterThe InquirerApple InsiderBBC NewsSky NewsGoogle Newsxkcddiodesign

    © 1999-2009 The Drobe Team. Some rights reserved, click here for more information
    Powered by MiniDrobeCMS, based on J4U | Statistics
    "RISC OS development is a waste of time with [Drobe's] aggressive attitude towards reporting and disregard of facts"
    Page generated in 0.0296 seconds.