▁▁▁▁▁▁⏐︎▁▁ 9127
asciilifeform: bvt: your posted tester has the actual abort commented out ( otherwise seems identical to diana_coman's ? )
feedbot: http://qntra.net/2019/02/spain-relitigating-civil-war-now-that-losers-hold-government/ << Qntra -- Spain Relitigating Civil War Now That Losers Hold Government
BingoBoingo: In other news, odometer on my meat just rolled over
asciilifeform: happy bd BingoBoingo !
asciilifeform: in other noose, instrument pr0n : http://www.loper-os.org/pub/misc/mx20/panel.jpg http://www.loper-os.org/pub/misc/mx20/inside1.jpg http://www.loper-os.org/pub/misc/mx20/achtung.jpg http://www.loper-os.org/pub/misc/mx20/inside2.jpg
asciilifeform: beryllium muzzle of the 'gun' is center top of 2nd photo. auto-exposure ionization gauge is on bottom of 4th.
asciilifeform: very solid 'vhs america' feel to the thing, ~70kg of pb.
BingoBoingo: asciilifeform: ty, and ty for the porn
mircea_popescu: BingoBoingo wait, you're just 30 ?!
BingoBoingo: mircea_popescu: 33
BingoBoingo: rolled over on the small digit
mircea_popescu: so...
mircea_popescu: btw : Franco is presently interned << interned means someone's in jail. interred means someone's in the earth.
BingoBoingo: fxd
mircea_popescu: also possibry teh tin women reference too obscure
BingoBoingo: I'll keep the tin women hasn't been meme'd hard enough in mind in the future
mircea_popescu: maybe just link it ; but even so i'm nopt sure what "uch offers and promises none of these cities would abide the tin woman passing his dick pic around to all her friends that aren't him" means.
asciilifeform: is franco even mummified ? ( or is not caught up to ru 'high tech' !11 )
mircea_popescu: nah.
mircea_popescu: it's been 50 years, by now it's just some specially-designated earth.
asciilifeform: ( phunphakt, the lenin mummificator maintenance folx are still inbiz )
asciilifeform: would be interesting if stalin were dug up, he was given same process but 0 maintenance since mid-50s
asciilifeform: to compare.
asciilifeform: ( hrusch had him buried, coupla steps away from mausoleum back door )
asciilifeform still not fully made sense of franco -- d00d was 'fuhrer' by sheer accident, after mola's plane crash , and possibly only won war cuz other side resembled gavin & co, 9000 rando 'hasta y per siempre' derpfactions
asciilifeform would like to dig up the worx of the http://btcbase.org/log/2014-01-16#446901 fella, but seems like the only surviving copy is in madrid national indianajoneswarehouse ☝︎
a111: Logged on 2014-01-16 04:40 asciilifeform: "Sewers caused all our troubles. The masses of this country are not like your Americans, nor even like the British. They are slave stock. They are good for nothing but slaves and only when they are used as slaves are they happy. But we, the decent people, made the mistake of giving them modern housing in the cities where we have our factories. We put sewers in these cities, sewers which extend right down to the
mircea_popescu: imo franco very much like maduro. i dunno if you've looked at dood much, he's 100% ranchero guy, would be way the fuck happier raising cattle, maybe at the most driving a truck. but he's stuck with these idiots.
mircea_popescu: ~same deal with franco.
mircea_popescu: asciilifeform how are you with osha btw :D
asciilifeform: !#s osha and vandal
a111: 0 results for "osha and vandal", http://btcbase.org/log-search?q=osha%20and%20vandal
asciilifeform: hrm.
asciilifeform: !#s hard hat mack
a111: 3 results for "hard hat mack", http://btcbase.org/log-search?q=hard%20hat%20mack
asciilifeform: ^ see also.
asciilifeform: http://btcbase.org/log/2014-02-19#516664 << ☝︎
a111: Logged on 2014-02-19 15:51 asciilifeform: brother and i played this on our 'Iskra' (xt clone) and combed three different dictionaries to learn what the fuck an osha is
mircea_popescu: lol
feedbot: http://bvt-trace.net/2019/02/gnat-zero-cost-exceptions-and-asynchronous-task-aborting-part-2/ << bvt's backtrace -- GNAT Zero Cost Exceptions and Asynchronous Task Aborting. Part 2.
diana_coman: bvt, interesting; is that gcc5-specific though?
bvt: i don't think it gcc5-specific, the patch against this problem that i've seen was written for gcc 4.8
diana_coman: hmm, now one wonders if the patch made it into gcc 4.9 or not
mircea_popescu: meanwhile in spamlulz, the great ukrainian clinic of surogate medicine drama : http://p.bvulpes.com/pastes/BrTQl/?raw=true
mircea_popescu: (as reported by diddled buyers of biotexcom organization of reproductive medicine)
bvt: diana_coman: it did not, as it was a clear hack to just make things work http://bvt-trace.net/src/gthr-disable-weak.diff
mircea_popescu: bvt "Before going into the detail" << that "detail" never takes an article, either definite or indefinite, for some reason to do with english being weird.
mircea_popescu: bvt --eh-frame-hdr << how much less probable does it make it ? (ie, there's a bunch of old reported stash smashing bugs in gcc, such http://btcbase.org/log/2019-02-16#1897096 as from yest), and --eh-frame-hdr protects the stack from being thus corrupted. ☝︎
a111: Logged on 2019-02-16 00:31 mircea_popescu: http://archive.is/x8D5k << apparently they STILL have the issue in gcc 8.
mircea_popescu: ie, if it makes it 100% less probable, "disappear entirely", then it's maybe the same thing ? and if not... could actually be two separate issues ?
bvt: it goes from crashing once in 3-5 runs to crashing once in approx 1000; however i've also seen deadlocks, which may be worse stuff to deal with than an honest crash.
mircea_popescu: hmm.
mircea_popescu: there are in fact two different issues there, aren't there.
mircea_popescu: incidentally, the http://btcbase.org/log/2019-02-16#1897098 seems an exact from-field description of the higher level http://bvt-trace.net/2019/02/gnat-zero-cost-exceptions-and-asynchronous-task-aborting-part-2/#selection-139.335-139.443 problem, doesn't it. ☝︎
a111: Logged on 2019-02-16 00:32 mircea_popescu: "The issue is that the code generated for __builtin_longjmp reads a value for x29 (the frame pointer) from the jmp_buf, but the code generated for __builtin_setjmp doesn't actually write x29 to the jmp_buf, leading to corruption of x29 when a longjmp occurs.
bvt: maybe there are two similar issues that are both 'cured' by switching to dynamic linking, but currently i don't think so. i'm using zcx runtime for these tests.
mircea_popescu: around gcc5 times (early 2016) binutils were verschlimmbessert with support of new relocations <<< aaahahahahaha.
mircea_popescu: "they were seriously improved"
mircea_popescu: that's a seriously great coinage.
mircea_popescu: bvt would you say "they were seriously improved" or "gravely improved" ?
mircea_popescu: or actually, "they were most greviously improved"
bvt: improved beyond repair?
asciilifeform: poetteringed
mircea_popescu: it's fucking beautiful. ^ is why german kicks so much ass, there's just no fucking shortage of poetry in it.
mircea_popescu: asciilifeform diana_coman can either of you package a bin for his bootstrap privately ?
mircea_popescu: no need to sign it, just encrypt it to him, so he's not stuck going to spamforge.barf/virusplox.htm.php
asciilifeform: iirc i uploaded a signed build... cant seem to find where grr
mircea_popescu: kk
asciilifeform: will bake new one
mircea_popescu: !!rated bvt
deedbot: mircea_popescu has not rated bvt.
mircea_popescu: !!rate bvt 2 http://bvt-trace.net/2019/02/gnat-zero-cost-exceptions-and-asynchronous-task-aborting-part-2/#selection-171.346-171.363
deedbot: Get your OTP: http://p.bvulpes.com/pastes/qWVuC/?raw=true
mircea_popescu: it's such a fucking pleasure to get up in the morning and get to the logs...
bvt: thanks!
diana_coman: I also tend to remember asciilifeform had at some point a signed build; anyway, if it's still needed I can pack ave1's gnat, yes; possibly he'd need both the "static-only" (i.e. latest version) and some previous version
bvt: static version should be fine. then would also try it on cuntoo (have it running, the genesis signature still does not match).
mircea_popescu: bvt dump the dir for trinque anyway, maybe it helps him. nobody suffered from too much data yet.
mircea_popescu: open source versioning system : verschlimmbessert, verfluchtbessert...
mircea_popescu: "/* ??? Glibc has for a while now exported __register_frame_info and __deregister_frame_info. If we call __register_frame_info_bases from crtbegin (wherein it is declared weak), and this object does not get pulled from libgcc.a for other reasons, then the invocation of __deregister_frame_info will be resolved from glibc. Since the registration did not happen there, we'll die. Therefore, declare a new deregistration entry poi
mircea_popescu: nt that does the exact same thing, but will resolve to the same library as implements __register_frame_info_bases. */
mircea_popescu: "
mircea_popescu: reading gnu code, always good for a facepalm.
asciilifeform: http://btcbase.org/log/2018-05-15#1813753 << bvt et al ☝︎
a111: Logged on 2018-05-15 21:38 asciilifeform: ok, apol. for log clutter :
asciilifeform: ^ ave1 gnat mirrored , circa may 15 '18
mircea_popescu: ty alfie.
asciilifeform: see linked thrd for what's what.
asciilifeform: np mircea_popescu
mircea_popescu: now in other lulz, check this out : http://archive.is/89adR#selection-9.9948-9.10055 "This is a special mix of insertion sort and heap sort, optimized for the data sets that actually occur." ☟︎☟︎
asciilifeform: holyfuq the opensores kunstkammer
mircea_popescu: with a (unproven) claim for complexity cap no less.
mircea_popescu: which doesn't seem right to me, either, but it might be built by induction from actual datasets, nfi.
asciilifeform: 'proof dun fit in the margin' lol
mircea_popescu: right ?
asciilifeform: mircea_popescu: it's prolly built by thumbsuction
mircea_popescu: i also find caps always truthier if you have log in there somewhere!
bvt: thanks asciilifeform, downloading
mircea_popescu: asciilifeform one of the larger, more impressive books in my parents' library was "welt der kunst". i couldn't read german, but mom explained it's "the world of art" so it populated my childish immagination for a full decade, until old enough to read it. by that time it disappointed -- not that anything could have lived to heights a kid might build in mind over years. ☟︎
bvt: trinque: genesis (does not verify) from successful cuntoo deployment: http://bvt-trace.net/src/genesis-14.02.2019.vpatch ☟︎
asciilifeform: mircea_popescu: aaah see on my planet kunstkammer is specifically peter's, with the 2headed foeti etc
mircea_popescu: yes yes, it is.
mircea_popescu: "curio cabinet" approx. but kunst is art, reminded me of teh whole thing, because guess what ? we all grew up with this idea foss/gcc/glibc/whatever "magic inside!!!"
mircea_popescu: turns out chewing gum
asciilifeform: aaha
asciilifeform had this 'third eye' moment some time circ '04 , when digging inside opensores lisps
asciilifeform: *circa '04
asciilifeform: bvt: http://bvt-trace.net/2019/02/gnat-zero-cost-exceptions-and-asynchronous-task-aborting-part-2/comment-page-1/#comment-7
mircea_popescu: coincidentally : is anyone from the adacore/gnat/gnarl/whatever days still breathing even ? or 100% bolix situation, "documents at warehouse, i am machinist in charge" ?
asciilifeform: mircea_popescu: adacorpse appears to be inbiz, but hard to say when last did anyffin useful ( see e.g. https://www.adacore.com/press )
mircea_popescu: and in likbez-mp : can anyone explain "weak symbols" as a concept to me without making it sound like a hack ?
feedbot: http://thetarpit.org/posts/y05/084-gutenberg-ii.html << The Tar Pit -- gutenberg.org part zwei, a dissection ☟︎☟︎
mircea_popescu: because i can't shake this very strong http://btcbase.org/log/2016-01-21#1379603 flavour from "we don't know if this symbol is defined or not so we half-define it just in case" ☝︎
a111: Logged on 2016-01-21 13:29 asciilifeform: 'if i make it what i think is the right size, it crashes!111'
asciilifeform: mircea_popescu: it's a hack, of exactly that species ( see e.g. https://archive.is/vTHJi )
mircea_popescu: "but the mechanism for symbol clashing exists for a reason"
mircea_popescu: asciilifeform why not do it properly then, get rid of symbol clashing as a concept altogether, let everything be the last thing it was and be done with it.
asciilifeform: mircea_popescu: cuz it'd break ~100% of extant c soup
mircea_popescu: "socialism doesn't do things properly, it's against the religion. errything must be sorta-halvsies and then forgiven. "
asciilifeform holds that the gnu sepsis is a direct and inevitable result of ~how c worx~
mircea_popescu: asciilifeform what about c makes you not know wtf you're linking ?
asciilifeform: mircea_popescu: the part where you can #include <foo.h>
BingoBoingo: <mircea_popescu> maybe just link it ; but even so i'm nopt sure what "uch offers and promises none of these cities would abide the tin woman passing his dick pic around to all her friends that aren't him" means. << ties into the second archive link where... gossip rags are trying to monetize his sexts
asciilifeform: without saying where is foo
mircea_popescu: asciilifeform so basically it all comes down to a gns absence issue ?
asciilifeform: or even 'v absence'
mircea_popescu: if they had fully qualified descriptors instead of "filename" it'd be all rosy ?
asciilifeform: not simply 'fully qualified' , but with knowledge of wtf the item ~is~
asciilifeform: as it is, there could be 9000 variants of foo, and on same machine you'll find 900 of'em
asciilifeform: and all , to naked eye, 'same'
mircea_popescu: yeah, needs a v.
mircea_popescu: treeless identity also meaningless.
asciilifeform: mircea_popescu: unixtardism suffers from the full spectrum of the idjicies outlined in that 'what gets mircea_popescu raging' article
asciilifeform: from rampant 'substitute unlikes as likes' and onward
asciilifeform: the proggies are shite not the least because author ~has nfi what he's throwing into the pot~
asciilifeform: and whole 'culture' of the lang is formed around this
mircea_popescu: (note that the tempting "obvious" approach -- describe foo then!!! -- is not only fucking broken, but broken in the exact way minsky wasted life trying to produce. there can not be ~description~, the only way to induce meaning in the machine is through filiation. v-produced foo has a very strict "wtf is it ??" answer associated, but also very fine and not structure-driven.)
asciilifeform: !#s ifdefism
a111: 7 results for "ifdefism", http://btcbase.org/log-search?q=ifdefism
asciilifeform: ^ for instance
mircea_popescu: in fact, there's a long line of illustrious ancestors who, having spotted this problem (wtf is foo ?!) attempted to solve it ~the very wrong way~, ie, by definition. hence not just ai winter, but microscopically naggum's sgi misadventures and so on.
asciilifeform: even e.g. #include <foo.h:e432850de89226c6745301a5932e30c5b09f260b9c850a5e76e8119f66b2f06f1798156138a1741aeff9c46ab90ff1d8ad97d9c089c7d76991a8b7ea8b104bdf> would've been improvement
mircea_popescu: you can not in fact define symbols after the fact (and i don't mean just the elf technical term -- all symbols). the only way to define a symbol is by its parents.
mircea_popescu: asciilifeform yes, but you see it as an improvement because you perceive it forces their hands down the right path, whether they want to or not. it's a rapeprovement.
asciilifeform: the infestation is deep enuff that you quite obv could not make above example actually build reliably on any extant unix. the entire notion of 'portability' as pictured by unixtards (i.e. powered by #ifdefism) precludes it.
mircea_popescu: BingoBoingo ah right, there was all that huh. american industries.
asciilifeform: 'what if you have a vax-flavoured foo.h' etc
asciilifeform: in turn, foo.h churns, churns, 9000 new versions in 6 months, cuz c intrinsically is a '10 lines contain 14 bugs' lang by virtue of sheer obfuscatory ugh ( who can say e.g. how many off-by-ones in http://archive.is/89adR#selection-9.11980-9.13314 ? in all possible calling contexts.. )
asciilifeform: spittoon -- is in 1 strand.
mircea_popescu: well my dear alfie... you build it and see if it crashes. when it stopped crashing, you either got rid of all off-by-ones
mircea_popescu: or else you have a workable even set of them
mircea_popescu: workably even*
asciilifeform: lol
asciilifeform: there's yer 'workable' set , right there, linked.
mircea_popescu: aha.
mircea_popescu: there's programmers, and then there's fuzzgamers. which are more like gamers than grammers.
asciilifeform: pogrommers. (in the words of an ex- asciilifeform chix )
mircea_popescu: asciilifeform i don't fucking get it, just HOW FUCKING MANY symbols are they dealing with here ? by the sheer desperation screaming out of the code you'd think a compile produces at least 5 trillion of them. ☟︎
asciilifeform: it does
asciilifeform: cuz it pulls in ~whole box
mircea_popescu: which it does not, when's the last time you had 1mn. wtf is all this tim's wondermachines steampunk idiocy for ? can just sort a fucking list
asciilifeform: 'dynamic link' makes it 'easy' to pull in literally trillion symbols.
mircea_popescu: nuts.
asciilifeform: ( with added 'bonus' that you dun even know ~which~ , necessarily, recall dload() )
mircea_popescu: but as a factual matter -- object files end up a few mb, and they're not 100% symbol by mass. you jsut can not have this many.
asciilifeform: dynamic! it dun even gotta appear in the obj.
mircea_popescu: oh ffs.
asciilifeform: can be computed at runtime.
asciilifeform: ( witnessed in e.g. koch )
mircea_popescu: so why all this bs, again ? just so nobody has to know what they;'re doing ?
asciilifeform: originally cuz iron & os babel.
asciilifeform: that's the prime mover.
mircea_popescu: gcc_assert (sizeof (const fde *) == sizeof (const fde **));
asciilifeform: ^ all gnutardisms are fulla this. cuz otherwise fat change anyone could come up with even a helloworld that builds at all.
asciilifeform: vtronicism-ducttape.
mircea_popescu: see, engineers are worse than whores. a whore might pretend like she's not working, but an engineer does inept shit like "/* This should optimize out, but it is wise to make sure this assumption is correct. Should these have different sizes, we cannot cast between them and the overlaying onto ERRATIC will not work. */" so as to ~pretend~ like he doesn't see WHY exactly he wants to take that code out. seriously, ooga-booga-bu ☟︎
mircea_popescu: oooga-booga-bubu ?
asciilifeform: whore in some ways has better working condition -- at least she knows will not have to fuck tyrannosaur. ☟︎
mircea_popescu: knows no such thing.
asciilifeform: whereas engineer entirely might be given such , as a routine matter
asciilifeform: mircea_popescu: cocks have at least something resembling a bound parameter.
asciilifeform: whore can look in guiness book and know approx what will have to take in. engineer on other hand will be given 'proggy may have to run on vax , and microshit, and ... '
mircea_popescu: btw, you ever encountered "Bărbaţii-s făcuţi din carne, femeile - din oţel. Ar fi trebuit să fie invers, dar Dumnezeu mai greşeşte şi el...
mircea_popescu: Femeile zic că-s din carne, bărbaţii că-s din oţel, şi de-aia e noaptea-ntuneric şi viaţa e un hotel..." ro poem ?
asciilifeform: loox familiar, i suspect it was in a trilema piece
asciilifeform: but cannot presently recall which
mircea_popescu: possibru!
mircea_popescu: (for completeness, approx - "men are of flesh, women, of steel. it shoul've been the other way around, but god's hunchback and not above mistakes ; women say they're flesh, men claim to be steel -- which is why it's dark at night and life a hotel"
mircea_popescu: asciilifeform in other news, if they ever send you to http://btcbase.org/log/2019-02-02#1891380 ima suggest your punishment be you hafta literate code extant gnu offerings. you may not change any code, just add comments. ☝︎
a111: Logged on 2019-02-02 01:57 asciilifeform: i suppose will also work a++ for asciilifeform's peine forte et dure!11
asciilifeform: iirc diana_coman already did some time in that joint , when walked koch's thing
asciilifeform: ( and asciilifeform -- trb ) etc
mircea_popescu: aha.
asciilifeform: asciilifeform does ~this for bread, currently, so arguably already condemned to this
mircea_popescu: diana_coman is there some way to count the linker objects next time you compile say eulora ?
asciilifeform: mircea_popescu: afaik in diana_coman's case it is trivial, cuz static link.
mircea_popescu: i really have trouble believing the trillion thing.
mircea_popescu: asciilifeform so what should i count, kernel ?
asciilifeform: objdump --syms eulora | wc -l
asciilifeform: granted this aint recursive
asciilifeform: ( i.e. satan himself only knows what syms ~each sym~ drags in ~internally~ )
asciilifeform: in particular elf you only see what it 'externs'
mircea_popescu: right ?
asciilifeform: you dun see what the called routines 'externed', cuz you had built the libs statically, they pulled in what they pulled in
asciilifeform: ( that part will no longer appear as exported symbols, obv )
asciilifeform: if you walk ~entire box~ and count symbols, you can get an approximation of the 'universe' count
mircea_popescu: objdump --syms eulora-0.1.2b/euclient | wc -l >>7
asciilifeform: ( this is where asciilifeform cannot resist to 'on bolix, you simply ask the box what all symbols are, and can get source for whichever you point at' etc )
mircea_popescu: ie, not very useful.
asciilifeform: i'm surprised answer wasn't '1'
diana_coman: mircea_popescu, I'm not aware of anything that actually does that reliably
asciilifeform: as i understand, it cannot be done reliably on a unix, period.
mircea_popescu: diana_coman myeah. i guess it'd take a patch on gcc, which is too much hassle atm.
asciilifeform: the process of linking is lossy from pov of symbol count.
mircea_popescu: ahahaha jesus fuck this is incredible.
mircea_popescu: "/* The count field we have in the main struct object is somewhat limited, but should suffice for virtually all cases. If the counted value doesn't fit, re-write a zero. The worst that happens is that we re-count next time -- admittedly non-trivial in that this implies some 2M fdes, but at least we function. */" ☟︎
asciilifeform: mircea_popescu: c linking is simply automated cut&paste.
asciilifeform: ahahaha typical
mircea_popescu: asciilifeform see, i got horse's mouth number instead : ~2mn. ie, i was right! HA-HA!
mircea_popescu: besides -- at least they function.
asciilifeform: lol right function, until you bake build where 2mil + 1
mircea_popescu: it adds a zero!
mircea_popescu: look for yourself, i've never seen such wonders in whole lyf before! http://archive.is/89adR#selection-9.20821-9.21149
asciilifeform: mircea_popescu: you gotta read the gnu malloc sores sometime. very similar 'thinking'.
mircea_popescu: anyway. seems gcc has a baked-in "max 2097152 symbols"
asciilifeform: ( spoiler : heapism per se is a solution to a problem that is ill-posed , and therefore impossible for malloc to be anyffin but an elaborate http://btcbase.org/log/2016-01-21#1379603 ) ☝︎
a111: Logged on 2016-01-21 13:29 asciilifeform: 'if i make it what i think is the right size, it crashes!111'
asciilifeform: mircea_popescu: rright, but that's ~per build~, and ea. build destroys symbols ( in the sense that they got statically pumped into the bin, and no longer 'exported' )
mircea_popescu: so ?
asciilifeform: so it tells you 0 about the total # of syms on the machine
mircea_popescu: it's per-instance-of-the-weirdo-optimized-two-head-horse-with-six-earhooves sorting mechanism above runs.
mircea_popescu: ie, the thing they "optimized" into insanity never actually has to sort more than mn-level items, ie, no ufcking need to be made out of boats floating on billiard table
asciilifeform: rright, and this process eats a buncha libs, with n1, n2, ... nN syms in ea., and shits out e.g. another lib, that exports only 7.
asciilifeform: so anyffin linking ~that~ will eat 7 + its own.
mircea_popescu: sure. but we're not discussing the same thing here.
asciilifeform: and produce e.g. lib with 2.
asciilifeform: i thought mircea_popescu posed q of 'how many symbols on machine'.
mircea_popescu: the problem was : as per http://btcbase.org/log/2019-02-17#1897450 seen in http://btcbase.org/log/2019-02-17#1897382 -- is there call or isn't there call for such elaborate nonsense. the answer to this problem lies in the size of the dataset, if truly huge then ~perhaps~, but if small certainly not. then we had a discussion to establish whether large or small, which died on the facts, but i resurrected on culprit confession : ☝︎☝︎
a111: Logged on 2019-02-17 14:45 mircea_popescu: asciilifeform i don't fucking get it, just HOW FUCKING MANY symbols are they dealing with here ? by the sheer desperation screaming out of the code you'd think a compile produces at least 5 trillion of them.
a111: Logged on 2019-02-17 14:10 mircea_popescu: now in other lulz, check this out : http://archive.is/89adR#selection-9.9948-9.10055 "This is a special mix of insertion sort and heap sort, optimized for the data sets that actually occur."
mircea_popescu: they themselves admit 2mn is an upper bound, BY WHICH TOKEN they themselves admit the complification was spurious.
asciilifeform suspects that the '2mil' figure they got from 'how many in kernel 2.6 and let's times three' or similar
mircea_popescu: quite likely.
mircea_popescu: well, either that or they o(N) + n log n for some values of N, n. ☟︎
asciilifeform: the type of people who cannot stomach this type of 'thinking', 'engineering', end up self-retiring from unixism entirely, they eat pistol, or learn to run a crane, etc
asciilifeform: this leaves who it leaves.
asciilifeform: y'know, sorta like how botulinum secretes its magic juice, so nuffin else eats the carcass.
mircea_popescu: ie, there's occasions where insanity has its place (go no further than http://btcbase.org/log/2015-04-29#1115740 ). but this fashion among the scriptkiddies/gnu-amateur crowd for insanity is improductive ☝︎
a111: Logged on 2015-04-29 13:25 mircea_popescu: "Put another way, grep sells out its worst case (lots of partial matches) to make the best case (few partial matches) go faster. How treacherous! As this realization dawns on me, the room seemed to grow dim and slip sideways. I look up at the Ultimate Unix Geek, spinning slowly in his padded chair, and I hear his cackle "old age and treachery...", and in his flickering CRT there is a face reflected, but it's my ex girl
asciilifeform: aka 'worse is better'(tm)
asciilifeform: ( with the bonus lul, that sometimes somebody walks in with a http://www.loper-os.org/?p=2906 , and then simply has to 'unhappen' )
asciilifeform: ( cuz, spoiler, 'worse' aint ~factually~ 'better' , aside from 'stupidity has infinite hit points' )
mircea_popescu: are you discussing the specific case of grep there ? because i do believe it's a sound tradeoff.
asciilifeform: it's 'sound tradeoff' until it aint (e.g. you have system where 'allcomers' can trigger a grep on a data set they crafted, and yer box grinds to a halt )
asciilifeform: mircea_popescu: applicable to all cases where gnarly 'optimized for typical, and we think we know what is typical'
mircea_popescu: but i do know what's typical in at least some cases. which is why my kitchen doesn't have a fast food counter.
asciilifeform: ( 'but asciilifeform ! grep aint meant to run on hostile inputs !' 'guess wat, unix aint meant to run outside of locked mit hall with 4 pdp-8 in it either' )
asciilifeform: mircea_popescu: yer kitchen is a closed system , in the http://btcbase.org/log/2019-02-17#1897470 sense ☝︎
a111: Logged on 2019-02-17 14:49 asciilifeform: whore in some ways has better working condition -- at least she knows will not have to fuck tyrannosaur.
mircea_popescu: you can't go around simply solving the most general case of everything. precisely because such a thing as closed system exists.
asciilifeform: i.e. mircea_popescu actually knows that it dun need a deep fryer cuz wtf , it cannot be spontaneously filled with mcd eaters
mircea_popescu: precisely.
asciilifeform: whereas unix..
mircea_popescu: yes ?
mircea_popescu: what, i get the luxury of a door lock but programming environment must take all comers ?
asciilifeform: unix tries to 'be all possible kitchen' and appears to 'succeed', via fraudulently slipping in 9000 unprincipled-exceptions (hardcoded limits, not only in gcc, but even 'ls' , see old thrd, and moar or less errywhere ) , and 'optimizations' ☟︎
mircea_popescu: myeah.
mircea_popescu: holy shit, EVERY SINGLE THING. look here : ☟︎
mircea_popescu: " /* Take care to ignore link-once functions that were removed. In these cases, the function address will be NULL, but if the encoding is smaller than a pointer a true NULL may not be representable. Assume 0 in the representable bits is NULL. */"
mircea_popescu: why the fuck would you use encodings SMALLER than the bus width ?!
asciilifeform: antediluvian os (e.g. tops-10 et al) at least had hard limits printed in manual
asciilifeform: rather than pretense of 'infinite'
mircea_popescu: and why would you assume what broken notation means.
asciilifeform: bonus: 'null' aint 0 on any extant box.
mircea_popescu: right ?!
asciilifeform: aaha.
mircea_popescu: why not pick FB.
mircea_popescu: i mean, FB and 00 are equally likely to be fragment of null pointer.
asciilifeform: cuz, see, he feels free to 'assume', because anyone who doesn't, who demands to ~know~ before shooting, will have dropped out of school when faced with unixtardation
mircea_popescu: i can't believe this works.
mircea_popescu: what "ask the fellows to patch gcc, fix this one error we have". wtf, how do i ask this ?!
asciilifeform: y'know , all those listservs where the muppets shit out multiple MB erry day , that's where they 'ask' one another
asciilifeform: ( naturally if you aint one of'em, can ask until the cows come home. recall mircea_popescu's letter to rms ? )
mircea_popescu: shoulda sent him some pennies, http://btcbase.org/log/2012-09-16#-267346 item cost the tard in question 500 bux or somethjing like that iirc. ☝︎
a111: Logged on 2012-09-16 01:14 mircea_popescu: no.
asciilifeform: and all of this sepsis, comes from machine where there aint (and cannot be) any such thing as global symbol space, where pointer does not store any info re wtf it points to, nor does a block of code know that it is a block of code , nor lolcat gif knows that it is an array, etc
asciilifeform: and in turn heapism hacks , from machine that has nfi how to partition memory meaningfully, etc.
asciilifeform: ( could go on, but i sorta have an entire www re subj... )
mircea_popescu: http://btcbase.org/log/2012-09-16#-267418 http://btcbase.org/log/2012-09-16#-267417 http://btcbase.org/log/2012-09-16#-267352 http://btcbase.org/log/2012-09-16#-267349 for context. ☝︎☝︎☝︎☝︎
a111: Logged on 2012-09-16 01:03 mircea_popescu: dude stop faking it, seriously. you, taaki and his sister showed up. nobody cares, fo reals.
a111: Logged on 2012-09-16 01:03 nefario: stallman seemed like he was going to cry
a111: Logged on 2012-09-16 01:12 Diablo-D3: why the fuck did rms even show up
a111: Logged on 2012-09-16 01:12 mircea_popescu: Diablo-D3 because by now not that many people can be bothered to invite him anywhere.
asciilifeform: could link to the x60 affair also.
asciilifeform: imho typical 'living mushroom' fare.
mircea_popescu: (the sister in question being the 15yo http://trilema.com/2012/amir-taaki-has-done-and-continues-to-do-huge-disservice-to-anyone-serious-involved-in-bitcoin/ schmuck was trying to sell for bitcoins as a "totally legit enterpreneurial enterprise" coupla years priors)
asciilifeform: ( asciilifeform's unifying theory, is that living in c ecosystem turns ~all~ inhabitants, after enuff yrs, into a kind of rms; sorta like black lung of coal miner )
mircea_popescu: and the entirely fucktarded morons go about talking of this same schmuck in terms of some heroism or other, truly there's nothing more disgusting extant or imaginable than "people themselves" with their "democratically elected options" and whatnot.
mircea_popescu: amir taaki is a dude who was trying to pimp his underage sister ten years ago. that's all, what the fuck already.
mircea_popescu: clearly immigration to the uk worked out.
asciilifeform: https://archive.is/xIdrE#selection-63.5240-63.6234 << oblig naggum.
asciilifeform: ( was re cpp, but entirely valid point re unix architecture in general )
mircea_popescu: aanyways, thanks to bvt 's reading material i am well spooked. wtf do we even do, now ?
asciilifeform: mircea_popescu: if it were asciilifeform's proggy, asciilifeform would http://btcbase.org/log/2019-02-12#1895596 ☝︎
a111: Logged on 2019-02-12 23:36 asciilifeform: the avionics people seem to use it, but they (near as i was able to learn) dun kill tasks at all, and regard any detected wedge as a http://btcbase.org/log/2019-02-12#1895456 condition
mircea_popescu: zcx doesn't work, sjlj is broken and glibc is beyond salvation.
mircea_popescu: asciilifeform the issue is to come up with a linking scheme we can actually use.
asciilifeform: mircea_popescu: unless i misread bvt's piece, the bugola is only triggered when tasks are permitted to terminate.
mircea_popescu: yeah ?
mircea_popescu: "house only explodes when you turn on water faucet" is not an answer here.
asciilifeform: so consider what the airplane people do. they dun terminate. instead populate with N threads, where N is the # of physical cpu, and they can idle or work as demanded.
asciilifeform: this btw is how asciilifeform implemented phuctor backend.
mircea_popescu: cute, but not useful. we gotta have a programming environment, not a programming cardboard.
asciilifeform: mircea_popescu: 'house explodes when i turn on the hydrogen faucet' 'why do you have a hydrogen faucet ?'
mircea_popescu: we do not agree.
asciilifeform: mircea_popescu: the real q is , what subset of the claimed extant functionality adds up to a programming environment.
asciilifeform: ( i.e. working subset )
mircea_popescu: we're kinda discovering by doing here. but user-controls-machine is certainly in there.
asciilifeform: this is factually not the case on unix tho. good % of the control is illusory ( see e.g. the zombie thread )
asciilifeform: or the 'seppuku of son'
asciilifeform: what we did, is to poke with awl until punctured some of the illusions.
mircea_popescu: i intend to approach hardware breakage at hardware level.
asciilifeform: that's asciilifeform's tack.
mircea_popescu: something like "keep two of everything and throw out anything that behaves in any way contrary to your illusion no matter what happens".
mircea_popescu: is a good start.
mircea_popescu: i find it works fine with people ; and it'll work doubleplusfine with hardware. let it adapt to my needs or die.
asciilifeform: it worx great with hardware. except when it's connected like on pc, where 1 hosed device can fandango over entire ram. or handled as on unix, where i/o will happily zombie out on unplugged $gadget etc
mircea_popescu: so it'll come to more boxes, whatever.
mircea_popescu: the principle ain't changing to fit the world.
mircea_popescu: s.mg is perfectly willing to eventually erect torture chamber where shamed boxes ritualistically destroyed for their sins.
asciilifeform: this is how the 'cloud' people ended up with their circus. 'pc is broken' 'what if you connect 9000 pc'
asciilifeform: mircea_popescu: i'm sitting in something quite resembling such chamber as we speak.
mircea_popescu: proof positive method works!!!
asciilifeform: to revisit orig upstack thrd : pc dun offer iron locks. so threading relies on software locks, that 'work' in the sense where gcc is relied on to shit'em out correctly. what bvt appears to have found , is that (under particular inputs) it doesn't.
mircea_popescu: so leaving hardware alone, "zombie thread because northbridge went south" etc -- we still need a linking scheme that works.
asciilifeform: this is theoretically fixable. the sad part tho is that gcc is a potentially ~bottomless well of these.
mircea_popescu: well, could also link against musl, ban glibc
asciilifeform: that was settled in 2015 iirc.
asciilifeform: glibc has 0 biz in tmsr proggy.
asciilifeform: quite obv, any fix will have to fix musl.
mircea_popescu: in any case, this is a major decision / inflexion point, and we truly need all hands on deck for this, i'm not equipped with the right chicken darts to throw at guts / read feathers thereof.
mircea_popescu: so is basically the idea what we want is to get sjlj to work on musl for ada proggies ? or what ?
asciilifeform: ( half the reason why asciilifeform dug out musl, is that it's compact enuff to be fixable, at least in principle )
asciilifeform: mircea_popescu: it already worx , afaik, on musl, ave1's gnat shits out strictly musl-static linkage. ☟︎
asciilifeform: but remains to be established if bvt's bug afflicts it.
mircea_popescu: some time to look at things and consider matters will be needed ; but i specifically want to hear something from asciilifeform ave1 bvt diana_coman phf spyked trinque ☟︎☟︎☟︎☟︎☟︎
asciilifeform: mircea_popescu: the diana_coman-bin we disasmed yesterday , is musltronic.
asciilifeform: as is all current test build of ffa, etc
mircea_popescu: asciilifeform yes. but to my knowledge to date musl was a preference rather than a standard. we never said "no more glibc linking" as we said eg http://btcbase.org/log/2018-09-19#1851879 ☝︎
a111: Logged on 2018-09-19 17:47 mircea_popescu: but anyway : NO NEW WORK ON SHA PLOX. USE KECCAK.
asciilifeform: mircea_popescu: imho the near-term thing to do is for bvt to get the gcc5sim, glibcism, out of his test setup. then can proceed to fix bugs that we actually have in the house, rather than liquishit that only afflicts glibctards.
asciilifeform: mircea_popescu: we did. recall the 'nss' incident.
mircea_popescu: link ?
asciilifeform: was found that glibc actually prohibits static linkage.
asciilifeform: !#s libnss
a111: 62 results for "libnss", http://btcbase.org/log-search?q=libnss
asciilifeform: e.g. http://btcbase.org/log/2015-04-29#1115985 ☝︎
a111: Logged on 2015-04-29 16:28 mod6: so libnss is dynamically compiled and built/linked to glibc, and can not be avoided?
asciilifeform: it was subj of mircea_popescu's letter to rms, and the associated lulz
mircea_popescu: http://btcbase.org/log/2015-04-29#1116015 << ? ☝︎
a111: Logged on 2015-04-29 16:41 mircea_popescu: you can't go "oh i don't use libnss anyway". you probably are.
asciilifeform: when uncovered that drepper (maintainer of glibc) deliberately broke static linkage globally
asciilifeform: this was a 2015 find. after which asciilifeform immediately proceeded to get glibc the hell out of trb.
mircea_popescu: http://btcbase.org/log/2015-04-06#1089996 ? ☝︎
a111: Logged on 2015-04-06 18:19 mircea_popescu: what's now needed is an expert computer engineer willing and able to take over maintenance of libnss, starting with fixing it so it allows proper static linking.
mircea_popescu: which line am i looking at here ?
asciilifeform: mircea_popescu: this was a ~3 month thread
mircea_popescu: ok but you're breaking form here.
asciilifeform: i dun think anyone's compressed it into a compact chronology of yet
asciilifeform: ( possibly nicoleci job ? )
mircea_popescu: yes, no glibc was in fact a preference, and we got it out, of trb, of eulora, etc. no argument there.
asciilifeform: and out of gnat.
asciilifeform: ave1's entire project.
mircea_popescu: nevertheless, we never actually said "do not use this".
asciilifeform: glibc is simply poison.
asciilifeform: ( e.g. 'bash bug', also drepper , also via glibc )
mircea_popescu: anyway, this can rest nao,
asciilifeform: item is ~10x the mass of musl, and fulla 'surprises' that erry time turned out to be architecturally baked in.
mircea_popescu shall give it some time to hear from people.
asciilifeform: aite
mircea_popescu: afaik everybody up until a week ago when http://btcbase.org/log/2019-02-12#1895231 nobody even compiled ada other than zcx. ☝︎
a111: Logged on 2019-02-12 13:12 bvt: during the gnat build, the sjlj runtime is built, so it should be possible to switch to it and test.
asciilifeform: mircea_popescu: until diana_coman's test battery, i never even attempted to use the tasking system.
asciilifeform: ( none of asciilifeform's items to date, called for it )
mircea_popescu: and i thought, naivity of naivities and unexamined infantilism of unexamined infantilisms, that sjlj is a quaint artefact of slow yore, meanwhile supplanted by more modern, better alternatives.
mircea_popescu: i actually thought this. i was still thinking this, feb 11th.
mircea_popescu: cuz no, http://btcbase.org/log/2019-02-17#1897391 never really goes away. ☝︎
a111: Logged on 2019-02-17 14:14 mircea_popescu: asciilifeform one of the larger, more impressive books in my parents' library was "welt der kunst". i couldn't read german, but mom explained it's "the world of art" so it populated my childish immagination for a full decade, until old enough to read it. by that time it disappointed -- not that anything could have lived to heights a kid might build in mind over years.
asciilifeform: mircea_popescu: near as i can tell , zcx is a http://btcbase.org/log/2019-02-17#1897558 , it attempts to implement multiprocess on ~all~ machines, incl. ones that dun have any support for interrupts (e.g http://btcbase.org/log/2019-02-12#1895612 ) ☝︎☝︎
a111: Logged on 2019-02-17 15:21 asciilifeform: unix tries to 'be all possible kitchen' and appears to 'succeed', via fraudulently slipping in 9000 unprincipled-exceptions (hardcoded limits, not only in gcc, but even 'ls' , see old thrd, and moar or less errywhere ) , and 'optimizations'
a111: Logged on 2019-02-12 23:41 asciilifeform: there's a lulzy 'pentagon standard' one, the name presently escapes me, iirc it is in the log tho
asciilifeform: mircea_popescu: ... nor is this the only instance of this kinda thing. consider e.g. https://archive.is/MxPlA#selection-14.407-2653.3
asciilifeform: they didn't include a word x word mul that gives you both halves. why not ? 'oh not all irons have a mul instr.'
asciilifeform: or 'can haz carry from add?' 'no, cuz not all irons HAVE carry flag'
asciilifeform: it's an elementary babel.
asciilifeform: asciilifeform's 1st step in writing ffa, recall, was to conceive of (and prove) an arithmetic workaround for above. that, right off the bat, cost ~10fold cpu.
asciilifeform: ( and when found that ~despite this~, http://www.loper-os.org/?p=2906 , was pant-shittingly hilarious, how koch still managed to be the tortoise in the race ) ☟︎
asciilifeform: this is rather like if 2 d00dz run, and the 1 carrying 100kg of lispmachine ends up winning.
mircea_popescu: anyway, let's draw some quick possible approaches here.
mircea_popescu: a. we make no standard, every man for his own, but : a.1. ada is the preferred language ; a.2. musl is the preferred standards provider ; a.3. zcx is the preferred exception mechanism ; a.4. static is the preferred build mode. this should come with a design process for candidates evaluation for standardization.
mircea_popescu: b. ada-sjlj-musl-static is the standard, and we simply don't sign or use anything that doesn't live up to this.
mircea_popescu: c. ada-?-musl-static is the standard, either zcx or sjlj is acceptable (mostly based on what threading philosophy one embraces), with an obvious preference for zcx if one doesn't thread. ☟︎☟︎
mircea_popescu: d. ada-zcx-musl-static is the standard for non-threaded programs, we don't standardize threading.
mircea_popescu: e. something else (among which possible e.1. someone reads and implements dwarf properly ; e.2. someone picks a glibc to grandfather and dedicates himself to cleaning and fixing.)
asciilifeform: re 'e', i can't picture what'd move anyone with two neurons to rub together to maintain a glibc, that'd be rather like starting a trb from prb 12 (or what is current one)
mircea_popescu: can import glibc 3.x or w/e.
asciilifeform: i dun see where drepperism wins in ~any~ version, vs. the ab initio and 10x moar compact musl.
mircea_popescu: asciilifeform current one prolly v49, note how gcc went from 5 to 8 in 2 years.
mircea_popescu: asciilifeform but it's not you who has to see, maybe someone sees, what. im certainly not sending you to e.2
asciilifeform: mircea_popescu: cuntoo is arguably a realtime test lab for 'what does removing glibc from ~errything~ cost'
asciilifeform: for instance, emacs has yet to be cured, as i understand ☟︎
mircea_popescu: so it is.
mircea_popescu: asciilifeform i very much don't expect you want the prb 12 that is emacs. rewrite yes ? :D ☟︎
asciilifeform: 'd' is arguably mis-statement of problem, a threadless proggy incorporates ~neither~ system
asciilifeform: ( as asciilifeform recently discovered re ffa. it dun thread, and gcc correctly snips out all pertinent coad )
mircea_popescu: asciilifeform still gotta build the ada environment ~with something~. ☟︎
asciilifeform: environment yes.
mircea_popescu: it was short form for that.
asciilifeform: aa
asciilifeform: given this, asciilifeform would go with 'b' + 'we fix the breakages , both as-we-find-'em and proactively '
asciilifeform: rather than continuing in a babelized gnat with 'pick yer threader, pick yer stdlib' etc
mircea_popescu: this pretty much bans glibc, from my unexpert cursory look it dun seem fixable for sjlj.
asciilifeform: i banned it for all asciilifeform-powered efforts in 2015, and dun miss it.
diana_coman: re glibc: until now I saw it as tolerated until full tmsr version (whatever that might be, i.e. owned glibc version or musl or whatever)
mircea_popescu: diana_coman looks like it's going the way of cuntoo-ada-musl, no glibc.
asciilifeform: diana_coman: the caveat is that i still dunhave a working cuntoo for all asciilifeform-operated irons; e.g. rk is still running barbaric old glibc gentoo
diana_coman: it does seem precisely so, yes
diana_coman: and asciilifeform beat me to it
mircea_popescu: asciilifeform getting an aarch64 musl sjlj going will be a fun task.
diana_coman: that's precisely why it was tolerated until now afaik: because all sorts not yet fully ported to anything tmsr
asciilifeform: mircea_popescu: entirely. see 2d ago thrd.
mircea_popescu: aha.
mircea_popescu: (on both counts, lol)
asciilifeform: i expect that i'm even doomed to open a book and see how the fuck arm64 worx.
asciilifeform: mircea_popescu: fix of sjlj on arm64 is actually moar urgent than arm-cuntoo, cuz sanely build ( static-musl ) ~will~ run on glibcistic linux
mircea_popescu: possibly, yeah.
asciilifeform: ( asciilifeform is for instance at this very moment sitting on a glibcistic gentoo box, but where all tmsr soft is musltronic )
diana_coman remembers that eulora client is 99% NON-tmsr
asciilifeform: diana_coman gets the trooly hard nuts to crack ( which is why retained by s.mg for coin , neh )
asciilifeform: ( asciilifeform also maintains multi-MB 'non-tmsr' proggies. for orc dubloons. it's how he eats )
diana_coman: to my mind option b has the benefit that it concentrates the effort in the right direction at least ☟︎
asciilifeform: ( the less said on the subj, the better, tho, my appetite already ruined by thinkin' about it )
asciilifeform: diana_coman: if it aint a seekrit: didja ever try building client on musl ?
diana_coman: asciilifeform, honestly, all I wanted was this game! lol
asciilifeform: heh
diana_coman: asciilifeform, no, but obv I will have to not try but do it
asciilifeform: rrright, was curious re the volume of barfola ☟︎
asciilifeform: ( e.g. asciilifeform was quite surprised when found that trb and ALL deps built cleanly & functioned on static musl ) ☟︎
asciilifeform: with ~0 modification
diana_coman has no curiosity on the topic: all pain at its time, not earlier
asciilifeform: fair'nuff
diana_coman: I don't know about option c i.e. whether there is something lost by going with it
diana_coman: I guess the main thing against it would be that part where can't kill
asciilifeform: diana_coman: the 1 use case i can picture for zcx, is on ultracompact irons. but even there, really, are we gonna use a http://btcbase.org/log/2019-02-12#1895612 somewhere ?! ☝︎
a111: Logged on 2019-02-12 23:41 asciilifeform: there's a lulzy 'pentagon standard' one, the name presently escapes me, iirc it is in the log tho
asciilifeform: that being said, sjlj is apparently totally broken on arm gcc currently, and if want a threaded proggy on e.g. rk, currently stuck with zcx
asciilifeform: ( for killing processes, it is possible to e.g. use ada.interrupts system . but asciilifeform not yet tested ! )
asciilifeform: ada.interrupts ~will~ have to be tested, it's a must for 'bare irons' adaisms as a class. ☟︎
asciilifeform: ( when build on unix -- it gets implemented as unix signals )
asciilifeform will brb : teatime.
diana_coman considers eating treebark: ate it before, certainly better than eating glibc-barf
mircea_popescu: http://btcbase.org/log/2019-02-17#1897739 << mostly benefit of correctly chosen version. no such wonder for eulora. ☝︎
a111: Logged on 2019-02-17 16:21 asciilifeform: rrright, was curious re the volume of barfola
mircea_popescu: http://btcbase.org/log/2019-02-17#1897740 rather. ☝︎
a111: Logged on 2019-02-17 16:21 asciilifeform: ( e.g. asciilifeform was quite surprised when found that trb and ALL deps built cleanly & functioned on static musl )
mircea_popescu: http://btcbase.org/log/2019-02-17#1897750 << tested nothing. fixed, gotta be ada not c. ☝︎☟︎
a111: Logged on 2019-02-17 16:26 asciilifeform: ada.interrupts ~will~ have to be tested, it's a must for 'bare irons' adaisms as a class.
mircea_popescu: also, subtle point in http://btcbase.org/log/2019-02-17#1897708 bears belabouring : the point is to standardize ~the tools~, not necessarily (in order) their usage, or end products. the idea is for user to know what to expect if builting a tmsr box, and why he expects that, not necessarily what he can do with it. ☝︎
a111: Logged on 2019-02-17 16:10 mircea_popescu: asciilifeform still gotta build the ada environment ~with something~.
mircea_popescu: he can use it to crush hymenoptera for all i care, just as long as it contains the correct set of software.
asciilifeform: mircea_popescu: plox to expand re http://btcbase.org/log/2019-02-17#1897758 ☝︎☟︎
a111: Logged on 2019-02-17 17:16 mircea_popescu: http://btcbase.org/log/2019-02-17#1897750 << tested nothing. fixed, gotta be ada not c.
asciilifeform: possibly i oughta add the detail, that $item is like any other machine i/o-ism -- on bare irons, it writes to the irq table ( whatever shape that has on $irons ) , on unixen it yes uses signals, because wtf else can you do there, on (hypothetical) msdos gnat, will again write to irq table, on boxen without interrupts -- will give eggog on build, what else; etc
asciilifeform: ( incidentally, when asciilifeform speaks of 'iron babel', interrupts are a screamingly concrete example : there is ~no uniformity b/w archs re how they're implemented (does it save regs ? which ? what happens if two interrupts temporally near ? ) or how many , or for what devices, etc )
asciilifeform: old msdos hands will recall setting jumpers for e.g. 'soundblaster' irq etc
asciilifeform: and conflicts.
asciilifeform: this was 'fixed' by intel (with obscene amt of direct standard authorship by microshit) by making the controller 9000x moar complex
asciilifeform: aka 'plug and pray'
asciilifeform: 'younger' archs that were baked with decent # of interrupts to begin with, have ~slightly~ less retarded subsystem
asciilifeform: afaik none of'em, however (with possible exception of sgi's) have semantics such that multiple processors dun share a bottleneck at the interrupt controller
asciilifeform: ( ever wonder why cannot make 'unhangable' os for multi-cpu pc ? this is why )
asciilifeform: all of this might seem uninteresting until you realize that this is what sits under all threading, no matter how implemented on os side.
asciilifeform: ( the very need for locking, on software level, for instance, comes from the absence of any sane mechanism for corralling data to particular cpu )
asciilifeform: concretely -- on sane iron, cpu do not share memory, but instead implement exactly diana_coman's work-queue mechanism.
asciilifeform brb,meat
feedbot: http://qntra.net/2019/02/chicago-actor-hired-nigerian-brothers-to-stage-hate-crime-hoax-indignant-at-getting-caught/ << Qntra -- Chicago Actor Hired Nigerian Brothers To Stage Hate Crime Hoax, Indignant At Getting Caught
mircea_popescu: http://btcbase.org/log/2019-02-17#1897763 << currently ada depends on a layer of c to do basic things such as abort. this can not stand, esp if we want an ada machine. that writing to irq table will have to happen through ada code, not calling c. ☝︎
a111: Logged on 2019-02-17 17:37 asciilifeform: mircea_popescu: plox to expand re http://btcbase.org/log/2019-02-17#1897758
feedbot: http://pizarroisp.net/2019/02/17/pizarro-isp-february-17th-update/ << PizarroISP -- Pizarro ISP February 17th Update
BingoBoingo: In old log gems http://btcbase.org/log/2012-09-16#-267555 http://btcbase.org/log/2012-09-16#-267554 ☝︎☝︎
a111: Logged on 2012-09-16 00:43 Bane_Capital: mircea_popescu: Well, I wish people would educate me instead of just beating on me.
a111: Logged on 2012-09-16 00:43 mircea_popescu: this is how we educate kids in europe
mircea_popescu: keks
mircea_popescu hasn't even the faintest who dood even was
BingoBoingo: Apparently a UStard seriously underestimating what he paid in total taxes
BingoBoingo: Anyways, All these names that had burned out completely before I showed up a few months later. History!
asciilifeform: mircea_popescu: by far biggest 'layer of c' is : the kernel.
mircea_popescu: true.
mircea_popescu: i suspect ada machine can be made with much tinier kernel tho.
mircea_popescu: so do you.
asciilifeform: i'm still curious what mircea_popescu thinks of as 'ada machine'
mircea_popescu: me too.
asciilifeform: heh
asciilifeform: BingoBoingo: http://pizarroisp.net/2019/02/17/pizarro-isp-february-17th-update/#selection-53.0-53.109 sounds interesting
asciilifeform: is this actually in the worx ? or still chalkboard
asciilifeform: mircea_popescu: thinking about it, kernel is really the starting point for 'get c the hell off the box' -- the e.g. 20% of gnat's standard lib that's in c, is in c strictly cuz of reason illustrate in http://btcbase.org/patches?patchset=udp , i.e. that kernel api doesn't eat sane (e.g. bounded array) parameters, demands liquishit c-istic buffers
mircea_popescu: entirely possible we'll have to do kernel-and-rest in one gulp
asciilifeform: seems like it.
mircea_popescu: though if possible, i'd just move the wrappers to ada first.
mircea_popescu: one advantage to c's retardation is that well... as long as you feed it the shit it expects, it'll work in the same manner as before.
asciilifeform: i linked the udp thing for a reason -- wrappers inescapably look like 'chunk of c', cuz headerola.
BingoBoingo: asciilifeform: I'm "knocking" on a few doors. The "polite way" hasn't been very productive, so the rapeful way is appearing very necessary. Haven't hear anything from the "Proud Boys", excess of ego appears to be a defect of the dwindling population of forum operators.
asciilifeform: BingoBoingo: mircea_popescu did say.
BingoBoingo: asciilifeform: Indeed
BingoBoingo: A large number of the folks who did or in the past would have started a forum are in the Google/Youtube hugbox or similar "watermelon farms"
BingoBoingo: Bizarre Characters gotta wank it
asciilifeform: mircea_popescu: the other major chunk of c, is of course the gcc backend.
asciilifeform: ( gnat dun have own back end, and afaik never did )
asciilifeform: y'know, the part that actually pisses out e.g. x86 instrs.
asciilifeform: ( locking bugs & all )
asciilifeform brb,meatsystems
BingoBoingo: <asciilifeform> i'm still curious what mircea_popescu thinks of as 'ada machine' << 128 bit MIPS 1, 2, 8, or 72 cores at 800, 1600, or 3200 mhz when purpose backed. Otherwise 128 bit for the UCI address space.
BingoBoingo: That's all I've got to guess atm
mircea_popescu: myeah.
mircea_popescu: actually ada not having a backend can (and probably will) hide all sorta surprises. ☟︎
asciilifeform: funnily enuff, i suspect there are a grand total of ~two~ ada back ends in existence : 1) the Official adacorpse one , sewed out of gcc ( the 'fsf gnat' is simply old copy of same )
asciilifeform: 2) bolix's
mircea_popescu: except latter only works for their own iron.
asciilifeform: could propose that there is a (3) , if one of the closed $maxint winshit adas actually implemented own, rather than stealing gcc's
asciilifeform: but i suspect ~those~ are all stolen gcc inside.
mircea_popescu: seems probable.
asciilifeform: mircea_popescu: potentially retargetable. but currently nfi if this is a useful shortcut to 'bake a backend'
mircea_popescu: myeah.
asciilifeform: at the very least, theirs is 50x moar compact than gcc.
asciilifeform: (i.e. ~readable)
mircea_popescu: problem with all this is -- the option's always between trust and knowledge. since we've discovered we can't trust gcc, it follows not only that we now have to write our own ; but that we must maintain the people who know how to write one.
asciilifeform: ( for n00bz: ) writing a compiler back-end aint actually hard. asciilifeform & many many other folx, did it ~as homework~ , at school. the hard thing is writing a ~decent~ optimizing backend. ☟︎
asciilifeform: it's why ~errybody is using gcc's (incl. the folx pretending not to)
asciilifeform: the other thing that makes backend a bitch is that ~100% of the work has to be done again and again, for each iron.
asciilifeform: ftr much easier for a sane iron ( with small instruction set ) like mips, than for x86.
asciilifeform: re bolix back end, i suspect it aint very useful as starting point, because was far ~too easy~ item , in that the iron per se was sane (i.e. performed bounds and type checks, so much of what gcc is stuck doing in soft, was unnecessary ) ☟︎
asciilifeform: if we had a sane iron, would be similarly easy to produce a back end ( and that's what asciilifeform thinks of as 'ada machine' ) ☟︎
asciilifeform: but presently we haven't such.
asciilifeform: ( this is where i point out, that the fabled 'sane iron' isn't simply a purely aesthetic win to ticke asciilifeform's aestheticles, but in fact substantially cuts down on the complexity of ~all other sane items~ that are to stand on top of it )
asciilifeform: *tickle
asciilifeform brb,food