asciilifeform: !w poll
watchglass: Polling 12 nodes...
watchglass: 205.134.172.26:8333 : Alive: (0.066s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=647322
watchglass: 205.134.172.27:8333 : Alive: (0.068s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=647322 (Operator: asciilifeform)
watchglass: 205.134.172.4:8333 : (172-4.core.ai.net) Alive: (0.125s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=647322
watchglass: 108.31.170.3:8333 : (pool-108-31-170-3.washdc.fios.verizon.net) Alive: (0.086s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=647322 (Operator: asciilifeform)
watchglass: 208.94.240.42:8333 : Alive: (0.118s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=647322
watchglass: 192.151.158.26:8333 : Alive: (0.162s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=647322
watchglass: 143.202.160.10:8333 : Alive: (0.217s) V=70001 (/therealbitcoin.org:0.7.0.1/) Jumpers=0x1 (TRB-Compat.) Blocks=647322
watchglass: 205.134.172.6:8333 : (172-6.core.ai.net) Alive: (0.074s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=647322
watchglass: 213.109.238.156:8333 : Alive: (0.377s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=647322
watchglass: 188.121.168.69:8333 : (rev-188-121-168-69.radiolan.sk) Alive: (0.317s) V=99999 (/therealbitcoin.org:0.9.99.99/) Jumpers=0x1 (TRB-Compat.) Blocks=647322
watchglass: 176.9.59.199:8333 : Busy? (No answer in 20 sec.) (Operator: jurov)
watchglass: 103.36.92.112:8333 : Busy? (No answer in 20 sec.)
trinque: asciilifeform: if you had to pick an assembler that wasn't gas, do you have a preference?
trinque: I've yet to find a bootloader that didn't bring in a pet assembler, be it nasm, fasm, etc
trinque: lilo brings in a whole toolchain (bin86) which imho makes it deceptively "simple". lilo+bin86 is what has to be measured if we're not doing the "hide the externalities" thing
trinque: otherwise I'm just gonna get out my pig-scale (cloc) and choose that way.
asciilifeform: trinque: i historically prefer 'yasm', with 'nasm' as edible alternative. they're both pretty fat balls o' overflowlang ftr. imho ideal endgame there would be as described in scriptlang thrd. but we aint there yet.
snsabot: Logged on 2020-08-08 14:24:33 asciilifeform: then rewrite the asmer, in same.
asciilifeform: trinque: re bootloaders, imho this'd be Right Thing.
snsabot: Logged on 2020-08-22 20:36:01 asciilifeform: http://logs.nosuchlabs.com/log/asciilifeform/2020-08-22#1020169 << imho a bootloader oughta fit in 512byte block, and is entirely acceptable to represent it as a script where e.g. xxd -r -p < << $stringofhexcoads . i.e. w/out an asmer dependency.
asciilifeform: imho demanding whole general-purpose macroasmer just to build 512b bootblock is massive overkill.
asciilifeform: ( tho otoh a linux w/out sumthing resembling one in the toolchain would be pretty useless )
asciilifeform remembers however the good'ol dayz of '80s micros where an asmer was thought of as unthinkable luxury
trinque: yep, totally agree that it shouldn't be needed. meanwhile lemme see which one used nasm. bbl
shinohai: ok trinque I saw the pentegram in the readme, do I sacrifice the virgin before stage-1 or stage-2 ?
trinque: house rules
asciilifeform: so far just one bugreport -- pentactle dun render on my tty, apparently uses utf8 bricks..
asciilifeform was under the notion that current battlefield vdiff detected these
asciilifeform still at the 'read the new scripts' stage, not yet attempted rebuild
trinque: huh, thought they were ansi blocks, but yeah, noticed they don't render right inside the env in at least vi and less (though differently wrong)
feedbot: http://mvdstandard.net/2020/09/ministry-of-defense-inks-deal-to-buy-two-hercules-aircraft-from-spain/ << The Montevideo Standard -- Ministry Of Defense Inks Deal To Buy Two Hercules Aircraft From Spain
verisimilitude: My MMC model is superior to the assembler model.
verisimilitude: I'm vehemently opposed to an x86_64 MMC targeting, as I don't believe the instruction set is even suited to an assembler, but the leagues simpler x86 may be in my sights, eventually.
trinque: verisimilitude: can I have a macroexpand on MMC?
verisimilitude: It's my Meta-Machine Code, trinque.
verisimilitude: Here is the primary article, and here is the latest article. Currently, only a CHIP-8 targeting exists.
trinque: I'll give it a look. this is however regarding the practical need to produce a usable boot sector for the item I linked recently.
verisimilitude: It's an advanced, interactive machine code development tool of mine own design, and I'm quite proud of the idea, even if my implementation falls short of my mind's eye's ideals.
verisimilitude: The tool is designed to produce or examine memory dumps, so an appropriate targeting would be very suited to that purpose, trinque.
trinque: I will perpetually be in the market for simpler items than the ones currently represented in the wad.
trinque: verisimilitude: what was the design problem you were trying to solve with mmc?
trinque: sounds more or less like an "IR"
trinque: verisimilitude: or is the idea closer to producing a "machine-code repl"?
verisimilitude: I don't recall a ``design problem'', per se. It's merely something I wanted to exist.
verisimilitude: I considered an alternative model for writing machine code whilst waiting on something, and mine idea borne of boredom became this.
verisimilitude: It's not an REPL, as it doesn't evaluate.
verisimilitude: It's not an intermediate representation, either.
verisimilitude: Upon pressing a key, questions are asked until sufficient information is provided, and then a human-readable description of the instruction is given, alongside the omnipresent information such as the unit value in several bases and the address.
verisimilitude: I recognized later it doubled as a tool for exploration, and there are some commands I want to add soon, such as finding an oft-referenced address to name it, and then have the tool add the association to all compatible instructions which reference the address.
trinque: documentation tool then, if it doesn't evaluate the instruction?
verisimilitude: Well, it's primary purpose is producing, but sure.
trinque: producing what?
verisimilitude: All its metadata contains is the purpose of the memory unit (instruction, value, etc.) and name association information, along with those names.
verisimilitude: I use it to write machine code programs, trinque.
trinque: perhaps I should read your articles before making you recite the item further in chat
trinque: but sounds interesting.
verisimilitude: I wasn't going to complain, but I'd appreciate reading what I've already written, yes.
verisimilitude: I'm flattered by the interest, trinque.