NRW.social

0 Beiträge0 Beteiligte0 Beiträge heute

Kroc CamenI feel like a madman -- my <a href="https://oldbytes.space/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> assembler, <a href="https://oldbytes.space/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a>, assembles itself! This is it doing so on an <a href="https://oldbytes.space/tags/Amstrad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Amstrad</a> <a href="https://oldbytes.space/tags/PCW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PCW</a> emulator, a <a href="https://oldbytes.space/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> CP/M machine from 1985. It's not optimised for speed on original hardware -- over 50% of the runtime will be just echoing text (thanks, CP/M) and I'm surprised by the amount of heap data needed in the end, but we are talking 335 KB of source code (8KB binary), and I can look into that<a href="https://github.com/kroc/v80" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/kroc/v80</a><a href="https://oldbytes.space/tags/asm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#asm</a> <a href="https://oldbytes.space/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a>

Kroc Camen<a href="https://oldbytes.space/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a> is released! I spent six months writing a <a href="https://oldbytes.space/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> assembler... in z80! <a href="https://github.com/kroc/v80" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/kroc/v80</a>Why? Because I see too much 8-bit software on GitHub that requires a PC toolchain to build -- if a computer can't produce and deploy its own software then it's not a computer, it's an appliance!These 8-bit machines should be *used*. What joy is there in retro or modern 8-bit hardware if you sit at your PC developing all day and deploying to it like so much throw-away web-scale infrastructure?But nobody should give up PC-based development either, so I made v80 runnable on PC too, allowing for build automation but never removing the ability to reproduce the software on real 8-bit hardware.Please, if your 8-bit software project can't be built on an 8-bit system, consider what you can do to change that. You don't have to use v80, but the idea should stick with you. Today's Windows XP is tomorrow's Windows 10. Your build system won't stop being a moving target you can't control.

Kroc Camen90% done with my <a href="https://oldbytes.space/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> assembler, <a href="https://oldbytes.space/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a>. The last feature is conditionals (i.e. conditional assembly if-statements) and finish up the read me. Supporting all z80 opcodes was a slog but it's still less than 4KB of code + a 4KB static binary tree that routes instructions to opcodes

Kroc Camen<a href="https://oldbytes.space/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> bros, your opinion on my z80 assembler's syntax please; <a href="https://oldbytes.space/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a> doesn't use standard Zilog syntax to make it significantly simpler (and faster) to parse, but if I want to create a Notepad++ language definition I don't have the flexibility there to differentiate registers (`add.b`) and keywords (`.b ...`)Please have a look at v80's syntax (<a href="https://github.com/Kroc/v80/blob/main/README.md" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/Kroc/v80/blob/main/README.md</a>) and tell me what you think. Could keywords start with something other than "."? (which could be reserved for private labels in the future). Should constants be ALL_CAPS instead of using a `#` sigil? I could allow separation of instructions and registers with spaces by letting the parser read 1 space in the instruction name as being any-number of spaces but using dots means multiple instructions on one line are easier to read and there's less typing and formatting overall<a href="https://oldbytes.space/tags/asm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#asm</a> <a href="https://oldbytes.space/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a> <a href="https://oldbytes.space/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a>

Kroc CamenGuys, that's a <a href="https://oldbytes.space/tags/Z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Z80</a> <a href="https://oldbytes.space/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> binary executing in the terminal on the right there. The incredible NTVCM is a program that runs your CP/M binaries right in the terminal like any other *nix program; <a href="https://github.com/davidly/ntvcm" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/davidly/ntvcm</a>It is necessary to grasp the full import of this -- software for 8-bit systems can be assembled on PC as part of any other build-script, makefile, GitHub Action, Docker, or whatever, but still retain the ability to build the software ON REAL 8-BIT HARDWARE.This is my Z80 assembler <a href="https://oldbytes.space/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a> (<a href="https://github.com/Kroc/v80" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/Kroc/v80</a>), written in Z80, running in <a href="https://oldbytes.space/tags/VSCode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#VSCode</a> producing a test binary. In the future it'll assemble itself, and then the possibilities are limitless<a href="https://oldbytes.space/tags/asm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#asm</a> <a href="https://oldbytes.space/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a> <a href="https://oldbytes.space/tags/retroprogramming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retroprogramming</a>

Kroc CamenDespite this <a href="https://oldbytes.space/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> code doing a neat math trick I'm going to drop it here because I don't think I'll be using it after all :(Here, we're parsing an expression; `@paren` is jumped to with the ASCII code for either "(" or ")" in A. We twiddle the bits and +/-1 to a counter based on the parenthesis used but without any branches!<a href="https://oldbytes.space/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a> <a href="https://oldbytes.space/tags/asm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#asm</a> <a href="https://oldbytes.space/tags/retroprogramming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retroprogramming</a>

Kroc CamenBut Kroc, <a href="https://oldbytes.space/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a> doesn’t even have a linker or macros, it can’t replace Z88DK &c.!v80 has a fixed level of complexity. Its goals are portability and cross-assembly; one day it will be Finished™️ rather than expanding forever. v80 is what you use to write a better assembler; macros, linker and all; or a C-compiler, whilst maintaining portability and the ability to bootstrap itself on new platforms.

Kroc CamenWhy not just use existing CP/M assemblers &| C-compilers from the past, eh, Kroc??Because <a href="https://oldbytes.space/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a> is more than that. Only 3KB is actual code. The other 3.7.KB is a static binary tree to map <a href="https://oldbytes.space/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> CPU mnemonics to opcodes. What if we replaced this static table with one for... 6502 instructions?Now we can assemble 6502 code on a Z80. Why would you even want to do that? Because you could use v80 to assemble a 6502 port of itself (v65?), even assembling z80 code on a 6502... and now you can bootstrap any code on any system using just 8-bit code runnable on 8-bit hardware using the same assembler syntax [but different CPU mnemonics], all whilst never giving up PC+GitHub but making it possible for anyone to develop 100% on retro hardware (if they choose) that can't hope to run Git and LLVM. Imagine being _productive_ on 8-bit hardware!

Kroc CamenIf a computer can’t compile and deploy its own software then it’s an appliance and not a general purpose computer.I see too much 8-bit software on GitHub require a PC tool chain (and God-forbid, LLVM) and this is bad because the 8-bit system can no longer speak for itself; the software may as well be proprietary for all that can be modified on the target.8-Bit software *must* be buildable on 8-bit hardware… but nobody should be required to abandon their PC or their GitHub workflow.<a href="https://oldbytes.space/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a> is the first, tiny step in solving this: A portable assembler and syntax that can assemble software on original hardware, but also on PC (and GitHub and Docker, or whatever) — currently via <a href="https://oldbytes.space/tags/RunCPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RunCPM</a> that runs <a href="https://oldbytes.space/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> <a href="https://oldbytes.space/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> executables in your terminal. (Please could someone make a <a href="https://oldbytes.space/tags/C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#C</a> version of v80 so that extra step is removed)Think about it — software written for 8-bit systems that can be assembled as easily on PC as current tool chains but doesn’t exclude doing so on real hardware too!

Kroc CamenA working <a href="https://oldbytes.space/tags/Z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Z80</a> assembler in 6.7KB. I'm not release-ready yet, but I'm getting there. The source code is extremely well commented so if you want to learn Z80 assembly and/or CP/M, start reading: <a href="https://github.com/Kroc/v80" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/Kroc/v80</a><a href="https://oldbytes.space/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a> <a href="https://oldbytes.space/tags/asm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#asm</a> <a href="https://oldbytes.space/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://oldbytes.space/tags/amstrad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amstrad</a> <a href="https://oldbytes.space/tags/pcw" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pcw</a>

Kroc CamenJust checking my <a href="https://oldbytes.space/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> assembler would run on real hardware...You won't find better commented, tighter, assembly code than this. <a href="https://oldbytes.space/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a> has been meticulously crafted with every routine sweated over for compactness, simplicity and elegance with a view to understandability.<a href="https://github.com/Kroc/v80" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/Kroc/v80</a><a href="https://oldbytes.space/tags/amstrad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#amstrad</a> <a href="https://oldbytes.space/tags/pcw" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pcw</a> <a href="https://oldbytes.space/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://oldbytes.space/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a> <a href="https://oldbytes.space/tags/retroprogramming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retroprogramming</a>

Kroc CamenBecause the CPU-specific bits are limited to a static table and a small lookup function, they could easily be swapped with something else like… a 6502 table :) Why would you want to assemble 6502 code on a Z80? Well what if we assembled a 6502-version of <a href="https://mstdn.social/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a> (v65?) which could reuse the static tables, meaning now you have a native 6502 assembler that can assemble itself but was bootstrapped on a Z80…

Kroc CamenFINALLY. That was hell, but my Z80 assembler in Z80 now parses all Z80 opcodes (794!) and unlike other native assemblers it uses a static binary tree to match strings to opcodes so the lookup code is only 179 bytes and the table is 3'733 bytes! <a href="https://mstdn.social/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> <a href="https://mstdn.social/tags/v80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#v80</a> <a href="https://mstdn.social/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://mstdn.social/tags/retroprogramming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retroprogramming</a> <a href="https://mstdn.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a>

Am WE unterwegs mim ZugWas ich so zur Zeit mache? Lokomotiven warten für eine Ausstellung in 5 Wochen. Sonntag hab ich mich hingesetzt und doch das Getriebe bei der Tesmo V80 (aus den 1960ern) gewechselt und sie Testrunden fahren lassen. Bis auf 5 Loks ist jetzt alles erledigt dann kommen die Waggons. 🤣 . <a href="https://nrw.social/tags/Tesmo" class="mention hashtag" rel="tag">#Tesmo</a> <a href="https://nrw.social/tags/V80" class="mention hashtag" rel="tag">#V80</a> <a href="https://nrw.social/tags/Diesellok" class="mention hashtag" rel="tag">#Diesellok</a> <a href="https://nrw.social/tags/dieselengine" class="mention hashtag" rel="tag">#dieselengine</a> <a href="https://nrw.social/tags/modellbahn" class="mention hashtag" rel="tag">#modellbahn</a> <a href="https://nrw.social/tags/modelleisenbahn" class="mention hashtag" rel="tag">#modelleisenbahn</a> <a href="https://nrw.social/tags/eisenbahn" class="mention hashtag" rel="tag">#eisenbahn</a> <a href="https://nrw.social/tags/h0" class="mention hashtag" rel="tag">#h0</a> <a href="https://nrw.social/tags/1zu87" class="mention hashtag" rel="tag">#1zu87</a> <a href="https://nrw.social/tags/1to87" class="mention hashtag" rel="tag">#1to87</a> <a href="https://nrw.social/tags/modeltrains" class="mention hashtag" rel="tag">#modeltrains</a> <a href="https://nrw.social/tags/modelrailroad" class="mention hashtag" rel="tag">#modelrailroad</a> <a href="https://nrw.social/tags/tischbahn" class="mention hashtag" rel="tag">#tischbahn</a>

Am WE unterwegs mim ZugModellbahn Abend! Mit der V80 und der E63 beides mit passenden Waggons. <a href="https://nrw.social/tags/M%C3%A4rklin" class="mention hashtag" rel="tag">#Märklin</a> <a href="https://nrw.social/tags/Maerklin" class="mention hashtag" rel="tag">#Maerklin</a> <a href="https://nrw.social/tags/Tesmo" class="mention hashtag" rel="tag">#Tesmo</a> <a href="https://nrw.social/tags/V80" class="mention hashtag" rel="tag">#V80</a> <a href="https://nrw.social/tags/1to87" class="mention hashtag" rel="tag">#1to87</a> <a href="https://nrw.social/tags/Modelleisenbahn" class="mention hashtag" rel="tag">#Modelleisenbahn</a> <a href="https://nrw.social/tags/H0" class="mention hashtag" rel="tag">#H0</a> <a href="https://nrw.social/tags/modelrailway" class="mention hashtag" rel="tag">#modelrailway</a> <a href="https://nrw.social/tags/modellbahn" class="mention hashtag" rel="tag">#modellbahn</a> <a href="https://nrw.social/tags/modeltrain" class="mention hashtag" rel="tag">#modeltrain</a> <a href="https://nrw.social/tags/E63" class="mention hashtag" rel="tag">#E63</a> <a href="https://nrw.social/tags/elok" class="mention hashtag" rel="tag">#elok</a> <a href="https://nrw.social/tags/diesellok" class="mention hashtag" rel="tag">#diesellok</a> <a href="https://nrw.social/tags/DB" class="mention hashtag" rel="tag">#DB</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#V80