Every assembler I have ever used has required that labels and symbols start at column 1, and that instructions, equates, etc., start at column 2 or later.
I'll have to see what I can do to make it more clear. Anything that starts in column 1 (other than a semicolon) should be considered a label, regardless of whether it's followed by a colon or not; but you should still use a colon to make searches easier. A label not starting in column 1 should ...
well, further research found me https://rosettacode.org/wiki/CRC-32 which conveniently provides 6502 assembly for CRC32. (in addition to an Apple II implementation!)
So I entered that and was a bit surprised to see it run in 3.4 seconds (faster than MY checksum generator), probably due to not using ...
It was not about getting a kind of checksum but getting a CRC32 computed as fast as possible on the 6502.
That's why I spoke up, seeing if a "lower quality" checksum would be acceptable, if it could run much faster. I suspect a CRC32 (or CRC16 for that matter) will be much slower than mine ...
My initial reason for making it is I needed a way to compare operating systems on different disk images. So i was looking for a "nearly instant" checksum on 256 byte blocks. I did actually consider CRC32, but for one a 32 bit checksum on 256 bytes seems like ...
just wondering, do you NEED it to be THE crc-32 digest, or do you just need something to do a decent job of detecting changes/ comparing blocks?
I needed a basic digest function recently, and coded something that produces what appears to be a good 2-byte digest of an arbitrary size portion of ...
I'm a bit late to the party, but welcome Virtual1, well done in constructing and thanks for sharing your unorthodox assembler.
Now that I've been working with it for awhile (and with an Apple IIe emulator instead of Apple ][ ) I've made some improvements to it - labels can have simple additions ...
Y'all need to find and read the bible, Beneath Apple DOS. PDFs available online in various places. https://mirrors.apple2.org.za/Apple%20II%20Documentation%20Project/Books/Beneath%20Apple%20DOS.pdf is one of them. It's an absolute gold mine of information concerning apples DOS. It doesn't have a ...
I have a disk which boots a machine code program I wrote. There is the classic "HELLO" file ('cept I named mine "IALIZE") but it's type B instead of type A or I. It runs on boot. Frankly, I have no idea how I did that.
There's a POKE you can do to change the file type it expects when it runs the ...
I've been soldering since I was 12, and it's been my experience that the iron is FAR less important than the hand it's in. Name brands just make your wallet lighter. Weller are nice but don't give you much more for the added cost. I used a Tenma for decades. (I've also used my share of butane irons ...
Welcome. From Table 5-7 of the 65816 data sheet at http://6502.org/documents/datasheets/wdc/wdc_w65c816s_oct_11_2018.pdf (the table also covering the '02), it looks like the longest A0 would stay constant ( not including STP and WAI instructions, or the 816's MVP and MVN instructions) might be four ...
I'm a bit late to the party, but welcome Virtual1, well done in constructing and thanks for sharing your unorthodox assembler.
thanks! I'm a big fan of "working with what you have". Most people either have Excel or use one of the free alternatives. And for simpler projects or patches, this might ...
I opened it in LibreOffice Calc (under Linux), and changed a branch to go do a different label, and it did its job just fine. No Microsoft.
For me the main benefits of an assembler are automatically adjusting the jump offsets, resolving subroutine addresses, translating opcodes, and of course ...