Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Brian Gregory Newsgroups: alt.windows7.general,alt.comp.os.windows-10,comp.sys.intel,comp.sys.ibm.pc.hardware.chips Subject: Re: Linux founder tells Intel to stop inventing 'magic instructions' and 'start fixing real problems' Date: Sat, 18 Jul 2020 13:04:27 +0100 Lines: 25 Message-ID: References: <1q8s3dvb888t.dlg@v.nguard.lh> <1rqenk95m4on0.dlg@v.nguard.lh> <170720201231335465%nospam@nospam.invalid> <180720200209021165%nospam@nospam.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net Xa3/z9uv6seWkhJSfItg1AsF6hMgmNiDUvVIF2e52lBhetzc3K Cancel-Lock: sha1:mB8WTBDV+ZzcywOOCA2M9Cehp/o= User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 In-Reply-To: <180720200209021165%nospam@nospam.invalid> Content-Language: en-GB Xref: csiph.com alt.comp.os.windows-10:117804 comp.sys.intel:721 comp.sys.ibm.pc.hardware.chips:2636 On 18/07/2020 07:09, nospam wrote: > In article , wrote: > >> >> We build little computers with parts. Then went to >> CPU. All assembly code! > > that doesn't make any sense. > Tiny CPUs often have tiny instruction sets that aren't well suited to any high level language. The first project I did on a PIC16C55 we did in assembler. It was not really too difficult. The whole thing fitted on about 3 pages. We did later get a "C compiler" for those chips but it was pushing it to call the language "C". It was mostly the syntax of C but nothing but static variables. Weird syntax to configure the chip the way you wanted. I can't even remember how you did I/O on it; must have been another weird extension to the syntax. It made it easier but not as much as you might think. -- Brian Gregory (in England).