log☇︎
18000+ entries in 0.011s
asciilifeform: 'Tarrio believes that unless President Donald Trump steps in, the de-platforming and dehumanizing of conservatives will continue. “He needs to step in, not only because if he doesn’t he will lose in 2020 with all of his supporters being kicked off social media, but because it’s the right thing to do,” Tarrio finishes.' << lol!! ☟︎
asciilifeform: historically i found that o3 is moar or less unusable for benchmarking anyffin, it risks to 'optimize away' unexpected pieces ( for instance, quite possibly your loop-and-mod-2 ) ☟︎
asciilifeform: ( ftr all 'canonical' ffa tests are built with o2 : http://btcbase.org/patches/ffa_ch16_miller_rabin.kv/tree/ffa/libffa/ffa.gpr#L56 )
asciilifeform: i assumed you used same flags for all shots
asciilifeform: aaa
asciilifeform: diana_coman: plox clarify what means 'fully optimized for time' here
asciilifeform brb,teatime
asciilifeform: mircea_popescu: this is why i like 'run 9000 shots, and discard outliers' (granted this only applies when the item is expected to go in constant time, goes without saying)
asciilifeform: ha
asciilifeform: ( depending on what you got in there )
asciilifeform: if yer proggy takes >=12h, this is certain to happen, it'll run up against cron
asciilifeform doesn't like benchmarks where 1 shot takes moar than coupla min, for the reason that unix box is a shitfest, liable to decide 'hey nao is the time to munge the fs' etc. and suddenly eat cpu for multiple min, whenever
asciilifeform: mircea_popescu: possibly was 'the peak of insanity'
asciilifeform: ( why -- cannot say until diana_coman returns with brief description of the irons )
asciilifeform: i'ma guess box ground to a halt during the 5-loops run, for a spell
asciilifeform: that's quite a few, even if you had nuffin in the middle of it
asciilifeform: so yes if you make 22, then 50 ^ 22
asciilifeform: in the pasted snippet, each outer loop multiplies the shots of inner by 50
asciilifeform: there are 50 even #s b/w 1 and 100 incl.
asciilifeform: how else
asciilifeform: mircea_popescu: 50
asciilifeform: diana_coman , when come back, plox to briefly describe the box
asciilifeform: based only on above, i suspect a case of http://btcbase.org/log/2019-01-10#1886261 ☝︎
asciilifeform: diana_coman, mircea_popescu : all of above is still just the baseline (no longjmpism) case ?
asciilifeform: *tries
asciilifeform tried to unravel wtf was found here
asciilifeform: imho whole day is a bit of overkill if for ~one~ shot..
asciilifeform: diana_coman: day+ ?! is this just 1 shot of benchmark, or many ?
asciilifeform bbl,meats
asciilifeform: what's hard to compute tho. you put sumthing on www, erry 2bit spamplagiarismbot mirrors it in 10sec, not even speaking of actual humans laffing
asciilifeform: http://trilema.com/2018/in-which-a-bizarre-character-wanks-it/#selection-541.3-553.157 << i always thought this was obv, and find it brainfucking that anybody dungetit
asciilifeform: i had nfi he was a proud , eh, son of persia
asciilifeform: (this was prior to mold going public re his 'kompyooting' )
asciilifeform remembers the roosh-v d00d, but for something quite else, iirc it was him who at one pt had asciilifeform's www linked as -- insultingly but lulzily -- 'the mencius moldbug of computing'
asciilifeform brb,meats
asciilifeform 1 day will post his engl. riff on subj, tailored for his particular shithole
asciilifeform: (~= 'the fuck you'll ever leave this shithole')
asciilifeform: or, say, pelevin's orcs sing their 'traditional folk song', 'Из этой жопы хуй уедешь'
asciilifeform: etc
asciilifeform: or 'fuck no you won't find' ~= хуй найдешь
asciilifeform: worx same.
asciilifeform: mircea_popescu: negation << >> 'нет ни хуя' etc
asciilifeform: ( so far impression is, roughly similar to '80s su, tho with ~less~ obv. leakage of suppressed laffter through the pg , oddly , i expected moar )
asciilifeform: it's funny , when asciilifeform went to 'museum of communism' in timis, pawed through buncha ancient lulzlit there, and photo'd 'a la minox' to read through laters and chew on the 'limba de lemn' ☟︎
asciilifeform: am o pula << i automatically recalled the http://btcbase.org/log/2016-06-21#1486093 rhyme ☝︎
asciilifeform: meanwhile, in n00b school, http://logs.bvulpes.com/asciilifeform?d=2019-2-13#461543
asciilifeform: asciilifeform often points out that we have buffer overflows on acct of the iron having nfi what 'integer', 'character', 'string', 'code' are , just pushes untagged words around; but it is also the reason why we have e.g. thread deadlocks (on an iron which 'knows' when yer e.g. assigning a variable, deadlock is ~impossible)
asciilifeform: in particular, http://www.loper-os.org/?p=55#selection-21.279-21.806
asciilifeform: ( for aficionados, see also e.g. http://www.loper-os.org/?p=55 )
asciilifeform: imho it is a curse on programming folx, that spackling seems to work as well as it does, really it is the equiv of eating 'tasty' pb paint chips, leads to grief always
asciilifeform: *zcx
asciilifeform: mircea_popescu: thinking about it -- 'zxc' strikes me as a classic case of http://btcbase.org/log/2018-10-25#1866191 and impedence mismatch generally. it was clearly written as attempt to 'deterministic scheduler on ??? iron/os', but fails, cuz you can't actually spackle away impedence mismatch b/w the underlying platform and the proggy ☝︎☟︎
asciilifeform: 16-bit thing, circa ~1980
asciilifeform: possibly http://btcbase.org/log/2015-03-12#1049461 . ☝︎
asciilifeform: orig ada-83 standard was baked when it was still king
asciilifeform: there's a lulzy 'pentagon standard' one, the name presently escapes me, iirc it is in the log tho ☟︎☟︎
asciilifeform: ( aside for weirdo 1970s chips with no interrupts... ) ☟︎☟︎
asciilifeform so far thinks -- if zcx actually measurably wins somewhere, i dun know where that is
asciilifeform: tricky to even answer this definitively, the conventional debug facility is shite for thrds
asciilifeform: ( which, perhaps surprisingly, unix permits )
asciilifeform: mircea_popescu: i don't specifically know, but suspect that the eggog happens when parent thread dies and (for moment) the children keep fandangoing
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 ☝︎☟︎
asciilifeform: imho zcx isn't actually of use on the current gnat, at all
asciilifeform: mircea_popescu: if (and only if) yer scheduler actually runs on the naked iron, a 'polled' sys gives ~less~ nondeterminism than a fully asynchronous one. but nobody's got this iron of yet.
asciilifeform: a linear process can still be heavy enuff (e.g. a 8192-bit primality test on ffa) that you wouldn't want to wait for it to finish when killing a thread
asciilifeform: if you have cppola ( or even, e.g., an asm-enhanced ffa ) in yer loop, it won't be poll-killable.
asciilifeform: errr, where yer proggy (rather than gnat) is on naked irons
asciilifeform: pollism may be suitable for an embedded sys, where gnat is running on naked irons, and the entire contents of the machine was built in 1 shot in the same gnat. but errywhere else it imho is liable to break.
asciilifeform: bvt: rright. my observation is, it aint suitable for a general-purpose kill switch , the prob orig. posed by mircea_popescu , cuz polled mode can only give ability to kill items which 'agreed' to be killable
asciilifeform: where you had to explicitly yield a thread, or whole machine ground to halt
asciilifeform: 'polled' mode seems to resemble the 'cooperative multitasking' found on ancient crapple and win9x
asciilifeform: bvt: my reasoning is based on the docs description of how implemented. but certainly worth a test, if anyone can be arsed ( given the 'all loops gotta be doctored' thing, my understanding is that 'polled' proggy would choke if wedges inside a cppism )
asciilifeform brb,teatime
asciilifeform: i.e. may as well be global
asciilifeform: bvt: whole point of multithreadism is to spread out the cpu-bulky work over cores, so i expect most cycles would be spend inside where enabled
asciilifeform: not to mention, the s.mg folx invoke external cppisms , and these won't have poll markers inside'em no matter what you do
asciilifeform: currently i suspect that polling (even if can be made to work errywhere) will be 9000x moar expensive than longjmpism ( the latter only adds to cost of exceptions, the former -- to ~all~ loops )
asciilifeform: aa
asciilifeform: bvt: m-c-m ?
asciilifeform: also ftr 'polling' knob does 0 on ave1 gnat. seems like it exists strictly for winblows.
asciilifeform: ( re what lose -- see logs. )
asciilifeform: afaik there is exactly 0 win from gcc5+, and plenty of lose.
asciilifeform: aa
asciilifeform: maybe musl implements some functionality is a way unexpected << where didja get a gcc5istic gnat built on musl, bvt ??
asciilifeform: i recommend to leave gcc5 entirely alone (unless specifically digging for lulz)
asciilifeform: gcc5 breakage extends into the Ada world << noshit, if yer on a gcc5istic gnat, all bets are off, they fucked the back end
asciilifeform: bvt: re the pragma polling bit : abort aint instantaneous, whereas the if A(I)'Terminated ... item happens immediately
asciilifeform: BingoBoingo: http://qntra.net/2019/02/madame-secretary-mike-pompeo-declares-huawei-deployments-obstacle-to-us-partnership/#comment-124253
asciilifeform: aa ty BingoBoingo
asciilifeform: http://btcbase.org/log/2019-02-12#1895192 << before this gets lost -- irix has reputation as stable, but porous as all fuck ( sgi never apparently gave half a shit ) ; not that we're at risk of cribbing from it, as you pointed out, 0 src ☝︎
asciilifeform: ( see e.g. ch15 ffa )
asciilifeform: longer obv. better, tho still need a # of independent runs .
asciilifeform: makes it quite tricky to get trooly precise timing for anyffing with serious cpu cost
asciilifeform: that sorta thing is maddening on unix pc.
asciilifeform: mircea_popescu: recall the http://btcbase.org/log/2019-01-10#1886261 incident ? ☝︎
asciilifeform: ( 1 moar reason why i'd like that msdos cross-gnat.. on msdos, the wall clock time is invariant )
asciilifeform: it's perfectly good, but to get decent resolution you end up needing gigantic # of repeats ( and unixism machine churn begins to drown the signal )
asciilifeform: ( so as to get actual ticktimes for this & other empiricals )
asciilifeform: i really gotta genesis my rdtsc asmism thingie for gnat
asciilifeform: ( would work so long as you take care to return. but i think that is obv )