log☇︎
16100+ entries in 0.109s
mircea_popescu: well, i won't trust my own understanding of asm and contemporary cpus as far as i can throw it ; but if indeed the operands in zcx impl were slower, you'd see it take less time!!!1
mircea_popescu: i agree with THAT part.
asciilifeform: on sane people planet i could determine this by reading the motherfucking docs
asciilifeform: i sawed it open to try an' see how thefuq the longjmp thing actually worx
mircea_popescu: (did i identify the same segment correctly ?)
asciilifeform: mircea_popescu: it's what gcc does for small (i dun recall threshhold) computed switch
asciilifeform: aah lol i'm a tard :
asciilifeform: the rest, i will omit, but also end up in the various unwindisms, aborts, stubs.
mircea_popescu: rather, i can't shake this impression that sjlj saddles us with two segments of overhead
asciilifeform: i suspect mircea_popescu dun habitually read gcc barf
asciilifeform: i.e. loox like is a flag that triggers an unwind
mircea_popescu: asciilifeform but i mean, test eax, eax ?
diana_coman: I'm atm doing the inventory of ave1's versions of gnat scripts and apparently even 2018-05-29 relies on downloading stuff that meanwhile moved/vanished as they always do; moreover, I have the darned stuff , now need to figure out how to cut out the download and just point the script at local source, ugh
asciilifeform: i'ma guess it is for word-alignment (why not ordinary nop ?? )
asciilifeform: ( will guess, tho i do not presently know, that these trigger unwind of stack )
mircea_popescu: (the 52 is cuz i took the 13 items and multiplied by 4, forgetting that these are actually byte alligned not 64-bit alligned)
mircea_popescu: no i know where you got the sub param from, what im asking is,
asciilifeform: i was discussing diana_coman's much earlier empirical find, that on ljmp stack fills faster per same # of calls. this here is why.
asciilifeform: ( before anyone asks, the 'unwind resume' variants are extern stdlib symbols, and i haven't looked to see how they differ yet )
asciilifeform: ty diana_coman ! i'ma look
diana_coman: asciilifeform, any preference re "pair of bins" i.e. the procedure calls or the loops of yest?
a111: Logged on 2019-02-11 01:33 hanbot: diana_coman fwiw i ran into a few broken internal links on ossasepia today on account of their still pointing to dianacoman.com, see http://ossasepia.com/2018/03/08/eucrypt-compilation-sheet/ fo' instance.
diana_coman: in other things, re http://btcbase.org/log/2019-02-11#1894896 -> this should now be fully sorted i.e. IP change for dianacoman.com propagated as far as I can see + redirection working fine for any link so please let me know if you still encounter trouble with any dead links; if you use only hosts (no DNS) then simply adding dianacoman.com on same IP as ossasepia should work seamlessly ☝︎
diana_coman: I still don't see the boo-boo of docs i.e ~"all programs should see a great improvement running zcx" or how was it
diana_coman: sorry; I should know by now to not hurry up with data report even if it's just 2 runs
mircea_popescu: aok. i can take my tin foil off now.
diana_coman: no, fat-fingered it, 0 instead of 9 i.e it was 0.93 not 0.03; sorry about that; still running atm the 1 handler with sjlj and then will move on to 2 and 3 handlers
asciilifeform: this does not contradict the hypothesis re handlers tho ( i have only the 'last chance' handler ). it does suggest that sjlj does not speed up ordinary calls substantially tho.
asciilifeform finds that (using pre-ave1 gnat, where i currently can --RTS=sjlj ) no detectable diff in mod ex
diana_coman: hence I suspect I fat-fingered it because I don't remember popping out when I read in console
diana_coman: and yes, then I'll do with 2 and 3 handlers too
diana_coman: ugh, either I fat-fingered there or what; let me run that again ; (and possibly /me should really stop getting data *other* than in a nice plain table)
diana_coman: aaand this is it, docs apparently right: fully cleaned up (i.e. none of the serpent vars + init anymore either), max value 16777216, x 22368144; with NO handlers it's 0.9s no sjlj and 0.03 with sjlj; same but WITH 1 handler per proc turns into 1.06s without sjlj and 158.87s with sjlj
diana_coman: i.e. same as above with Max at 16.77mn (but real X at 22.36mn) without sjlj -> 0.9s
diana_coman: mircea_popescu, just to make sure you get this straight: Max is one thing, the final X is another i.e. the final X really counts how many times procs got entered; the max value means procs stop calling others (but note that the x=x+1 is done before the check precisely because I wanted to know how many calls)
diana_coman: ugh, I still have that 1 exception handler per proc and with sjlj it overflows ofc; let me re-run it wihtout any exception handlers in it first, both with and without sjlj
mircea_popescu: a cool. ok, so 22mn takes 1.25 s i'd say it's in the zone, and we're good as such.
diana_coman: I fixed the stack issue
mircea_popescu: diana_coman i don't get it, so it crashed with 16mn but worked with 22mn ?
diana_coman: not on this one, I tried it
diana_coman: apparently I need to dig into this more
diana_coman: uhm, I set ulimit -s 900000 ; it shows, confirmed at that with either ulimit -a or ulimit -s; set it from the linker option too; prog still overflows in the end; and if I try MORE than that from ulimit -s I get bash: ulimit: stack size: cannot modify limit: Operation not permitted
asciilifeform: mircea_popescu: i've had to up stack depth on 1 occasion before -- when testing ffa with ridiculously wide bitnesses ( recall, item runs 100% stackistically )
mircea_popescu: so setrlimit to whatever is reasonable (here i'd expect no less than 832mb)
diana_coman: uhm, it overflows the stack and either the linker switch I'm using is not working or it can't make it
asciilifeform: diana_coman: fwiw the noise floor on e.g my test box, is 0.003 (i.e. a proggy with empty main)
diana_coman: <diana_coman> oh, no serpent in there ? it'll run VERY fast though i.e. 0.039s sort of thing -> darn, that's 0.0039
diana_coman: confirmed: with max=65535, no serpent (i.e. empty calls only), I got 0.004, 0.009, 0.007, 0.005 (without sjlj)
diana_coman: oh, no serpent in there ? it'll run VERY fast though i.e. 0.039s sort of thing
asciilifeform: mircea_popescu: i cannot resist to ask, is it 'ragassa' and not 'ragazza' ? ( was it a sicilianism or wat )
asciilifeform: aite, i'ma do it to the variant mircea_popescu goes with
diana_coman: atm I still have to get to the bottom of the "ave1 gnat with sjlj"
a111: Logged on 2019-02-14 16:05 asciilifeform: btw , to go with http://trilema.com/2019/so-what-is-the-man-saying , really oughta disasm a zcx variant and longjmp side by side and see what actually changes. ( when diana_coman comes back with working bins, i'ma set this up , for thread-co)
asciilifeform: diana_coman: if you have time, plox post a pair of bins so that i can http://btcbase.org/log/2019-02-14#1896414 tonight ☝︎
diana_coman: re http://btcbase.org/log/2019-02-14#1896383 -> http://p.bvulpes.com/pastes/o2h67/?raw=true (that's the version including a handler and obv, there are in fact 3 procedures A, B, C, with each calling the other two or one of the other two; MT is the Mersenne Twister Ada implementation I did for the UDP test) ☝︎
a111: Logged on 2019-02-14 07:40 diana_coman: http://btcbase.org/log/2019-02-14#1896320 -> hm, trinque, do you suspect it's really just down to V version? I can easily re-run the thing with a V pressed to same node as yours to rule that out, if that's the case
mircea_popescu: consider the math : i go out to eat, i eat at $100 a plate joint. i go out for a show, or a bender, or a casino trip, or what have you, i come back thousands lighter. meanwhile what's your living space, 100 sqm ? 1000 sqm ? you'll get fucking lost in an acre, really. with modern insulation what's the lossage, a few cents a day ? how THE FUCK will you care so much about the cent as to go cold rather than use electricity, while
phf: i've been looking at getting x11 working for cp101a but not on top of cuntoo. i'm going to take a break and attempt a build myself. i might run into the issue also
phf: trinque: i'm going to play with some link combinations, but perhaps it would be worthwhile to at least check if the named file exists on the system after failed genesis production.
mircea_popescu: and once they go away, what will i use ? there's a case for using electricity for heating if MOST of energy produced is electricity. because heating relatively small outlay, all things considered.
mircea_popescu: but the natgas will run out ; and the little house-sized powerplants that it enables will go away, i can't burn pitch in there.
asciilifeform: ( and ftr i dun hate winter, either 'bitcoin' or of the ordinary kind, winter is a-ok for so long as you aint stuck in the wind w/out a coat )
mircea_popescu: anyway, re above trends : there's a very visible trend in energy generation away from low quality and towards high quality. this means absolutely a move away from everything and into nuclear. as nuclear increases and fossils drop, the outlook will significantly change -- eg in romania i'd have not even considered heating on any other premise than natgas ; bathroom had eg towel rack consisting of hot water pipes and other such
asciilifeform: i dun read 'soshulmeadia', dun have any data other than 'no one seems to be offering 20k orc dubloons for coin like yr ago, just nao'
mircea_popescu: i dunno how i could say that, looking at teh data. it's not about what social media says, nothing ever is.
phf: http://btcbase.org/log/2019-02-14#1896331 << no. i gather you're not seeing this issue on your own machine? vdiff treats links the way diff did, as a completely new file, including the content ☝︎
mircea_popescu: so i expect to see it before i die, but i do not expect to spend anything on it this mid term.
mircea_popescu: why necessary event has not happened yet is sometimes explicable (if sun will burn out eventually, then why not yet ?!?!) but not always (say mom, if i'm gonna lose my virginity eventually, how come no girl fucked me yet ?!?!?!")
asciilifeform: right. so hypothesis requires then that it is viable commercially, i.e. someone other than mircea_popescu give enuff damn to bake'em into tiles.
mircea_popescu: because i don't care about tiles enough to make my own yet.
mircea_popescu: but i don't care what it costs in the sense i will have it done, not in the sense that i will have it done in the most expensive way possible. if there's bitcoin mining tiles and simple tiles available, i am buying the former.
mircea_popescu: and i don't care what it costs
mircea_popescu: because i WILL heat my bathroom floor so my whores can suck my cock barefoot rather than live in frigid 80s sovoklands.
asciilifeform: let's stipulate that this is true (i.e. that what's sold to konsoomer currently is only coupla notches obsolete.) i thought that orig 'heat house' hypothesis was re arbitrary degree of obsolescence.
asciilifeform: what instead should i call miner that eats 500 $ / mo of current to produce bitcent ?
a111: Logged on 2019-02-14 16:54 asciilifeform: ( i'ma take mircea_popescu's word for 'they are available to konsoomer' , evidently currently worth slightly moar as chump bait than as ore )
asciilifeform: i.e. scarcely ever <0C
asciilifeform: BingoBoingo: as i understand , BingoBoingostan is theoretically idea heatpump country
asciilifeform: i used to live in 1, erry flat had buncha resistance heaters, fuses regularly blew .
asciilifeform: ( i'ma take mircea_popescu's word for 'they are available to konsoomer' , evidently currently worth slightly moar as chump bait than as ore ) ☟︎
asciilifeform: this is where i confess that i did not follow the subj actively in recent yr or 2, last time i tried to buy miner was some time during kako's reign
asciilifeform: i can actually picture orcs heating with old miners, if they had the two neurons to rub together and get a boat loaded with'em
asciilifeform: i.e. this will go approx same as the jp dream of 'home reactor'
asciilifeform: i suspect that 'heat house' aint happening, no matter what level of 'important'. obsolete miners even nao aint worth the cost of transport , floor space, or fan dusting / noise isolation, even to use as heater. whereas 'current' iron is ~unobtainable to commoner on acct of being a strategic good. and can't picture how this would change as 'important' goes up.
asciilifeform: btw , to go with http://trilema.com/2019/so-what-is-the-man-saying , really oughta disasm a zcx variant and longjmp side by side and see what actually changes. ( when diana_coman comes back with working bins, i'ma set this up , for thread-co) ☟︎
mircea_popescu: asciilifeform but if i don't adjust the linux max for eulora, why the fuck would i care to do so for this test ?
mircea_popescu: re the loops, i don't see the point in bothering with this there. we were checking loops, not the whole call mechanism, there.
diana_coman: few cases I mean
mircea_popescu: (honestly i never heard of a program that properly used 64k stack frames ; seems if truly one needs such depths, one's welcome to fucking rewrite something, recursion be damned.)
mircea_popescu: set max value to say 65536 (this should result in <mb stack load, i am guessing ?) and let it run.
mircea_popescu: i can't believe we manage to have crosstalk with just two people talking.
diana_coman: ada's checks raise exceptions yes; not handled; I don't know if additional explicit handlers ADD or not
mircea_popescu: i can't even figure how it'd be broken, but yes.
diana_coman: being starter, I preferred not to force a choice there; but at any rate, if the previous node is basically broken as I gather that's certainly a problem
mircea_popescu: but i mean, your code would have handled exceptions if they arose, yes ? if a for looped out of bounds, or whatever. isn't it so ?
diana_coman: re re-pressing to his node - note that that is re v-tools in fact; and I pressed the v-starter to node before that precisely because it essentially forks there i.e. there are 2 options
diana_coman: hm; I don't know if it's exactly the same thing or not; perhaps it is
mircea_popescu: and yes, i would say it's worth re-pressing to his node and seeing if that fixes it. if it does, we'll have some 'splainin' to do.
mircea_popescu: trinque let me know how close i got. ☟︎
diana_coman: http://btcbase.org/log/2019-02-14#1896320 -> hm, trinque, do you suspect it's really just down to V version? I can easily re-run the thing with a V pressed to same node as yours to rule that out, if that's the case ☝︎☟︎