asciilifeform: they're replaced with the slice expression

asciilifeform: they don't exist

asciilifeform: no moar x0, y0, etc

asciilifeform: mod6: because we can't use the shorthand any moar

asciilifeform: they're the foundational abstraction that makes the thing compact and readable

asciilifeform: mod6: to understand ffa, you absolutely gotta grasp how ada array slices ( which Always Do The Right Thing ) work

asciilifeform: get what?

asciilifeform: but no copying of the input

asciilifeform: mod6: same

asciilifeform: mod6: 'if grandmother had balls..' (tm)

asciilifeform: you can't 'similar to the original' , it would BE the original

asciilifeform: e.g. the one you quoted

asciilifeform: the changed lines, what else

asciilifeform: if you do this, you get the original, what else could you get

asciilifeform: mod6: i dun understand the question

asciilifeform: mod6: below noise floor

asciilifeform tries to count how many 'improved' versions he wrote, and then discarded...

asciilifeform: ( and it ain't even over yet )

asciilifeform: this is perhaps the most pedantically massaged item asciilifeform ever wrote, this thing

asciilifeform: )

asciilifeform: ( the whole thing is quite compact, and misering on codesize loses massively moar than it wins here. (

asciilifeform: hence why everything that oughta be inlined, i empirically determined, and already is.

asciilifeform: the inline thing may seem like premature optimization, but function calls in ada are quite expensive, because bounds checking. so it makes MASSIVE difference.

asciilifeform: ( and it ain't an instance of 'compiler too smart for own good', either, but perfectly legitimate refusal to try to fill up the universe with your mistake )

asciilifeform: it will

asciilifeform: i thought this was clear...

asciilifeform: mod6: you can't inline a recursive call because this'd be logically equiv. to making the program infinitely long

asciilifeform: ( in so far as i can tell, it indeed respects the standard, and preserves control flow as written )

asciilifeform: gnat ain't supposed to unroll. at all.

asciilifeform: ^ for readers who wondered why karatsuba is the 1 routine in ffa ~not~ inlined... think.

asciilifeform: gcc will give you a very special eggog, even

asciilifeform: ( picture this )

asciilifeform: mod6: you can't inline a recursive invocation, wtf ☟︎

asciilifeform: 'this' being, if it wasn't obvious, the powerof2 constraint thing.

asciilifeform: but as it happens, my hypothesis re 'this will speed up mult' is wholly false; and the one where 'it will simplify program from reader pov' also, somewhat paradoxically, false.

asciilifeform: mod6: idea with this item, is that L is a power of 2 always. in 'classical' one, L can be anything (e.g. a 192-bit ffa ends up 3*64 on my box, i.e. L=3 )

asciilifeform: ( no moar foo.Z , now just foo )

asciilifeform: and to simplify reading.

asciilifeform: ( to enable building with all oopism banned )

asciilifeform: i abolished the 'record' thing

asciilifeform: mod6: almost certainly is

asciilifeform: mod6: see earlier thread

asciilifeform: http://wotpaste.cascadianhacker.com/pastes/YoOl3/?raw=true << 'classical' versions of all 3 routines above, for comparison.

asciilifeform: at least not from a mechanical pov.

asciilifeform: so it turns out that imposing 'powers of 2' is NOT a win.

asciilifeform: also imho the item above is LESS readable than the original.

asciilifeform: but apparently does 0 for us in the expected application.

asciilifeform: this kind of optimization could be interesting if we were dealing in MB+ ffaism

asciilifeform: so reducing temp space, does 0.

asciilifeform: i suspect that the reason is that the op fit in cache ANYWAY even prior

asciilifeform: which is surreal.

asciilifeform: ~no measurable speedup

asciilifeform: nope

asciilifeform: how this can be -- remains a puzzler.

asciilifeform: despite 50% reduction in temp space used by karatsuba mult and square

asciilifeform: however, the expected speedup did NOT materialize !!

asciilifeform: it is an implementation of http://btcbase.org/log/2017-08-14#1697730 ☝︎

asciilifeform: in other enigmas : http://wotpaste.cascadianhacker.com/pastes/5q4lR/?raw=true

asciilifeform: yeah i thought also.

asciilifeform: iirc the details of this tale are in last summer's l0gz

asciilifeform: ( why even asked? because insurance pays 0 w/out police docs )

asciilifeform: http://btcbase.org/log/2017-08-14#1697933 << pretty easily. asciilifeform had a bumper wreck in bmore once, passing cop declined to take report, demanded 'who was killed here? if nobody, i have no time for this, and no one else from station will come either' ☝︎

asciilifeform: http://btcbase.org/log/2017-08-14#1697917 << pupil only contracts if ~whole retina is illuminated. hence 'do not stare into laser with remaining good eye' ☝︎

asciilifeform: dafuq

asciilifeform: which is odd, because i still see the bots !

asciilifeform: asciilifeform is showing up in Framedragger's log but not phf's or ben_vulpes

asciilifeform: or massive netsplit

asciilifeform: phf: ??

asciilifeform: a111 broke??

asciilifeform: 'can't fight enemy who has outposts in your head' or how did it go.

asciilifeform: betcha shannonizer could at least match quality of shinohai's link

asciilifeform: student exercise : write a generator of 'shocking crises coming to bitcoin!!!' crapola

asciilifeform: half-digested, regurgitated matter

asciilifeform: in the most narrowly technical sense of the word

asciilifeform: it reads like barf

asciilifeform: and incidentally, open fpga trivially yields sdr.

asciilifeform: ( via radio, lan cable strung through window, whichever means. preferably transparently of layer.)

asciilifeform: this means a node that can speak directly to another.

asciilifeform: other idea is to demonstrate that trb can work without riding on top of existing telecom structure.

asciilifeform: ( and is the principal reason why there even is cabal )

asciilifeform: it ~would~ be a problem for any would-be defector from cabal

asciilifeform not equipped to say at present how much of a problem

asciilifeform: getting new blox to the transmitter asap would, theoretically, be a schelling point for miners ( all of whom currently 'eat the spoon of shit for free' from withholding chains )

asciilifeform: ( withholding in particular )

asciilifeform: it would make the kind of miner monkey work currently fashionable, ~impossible

asciilifeform: but if it isn't obvious why :

asciilifeform: *pow

asciilifeform: ( see old thread )

asciilifeform: relatedly, a shortwave ( or even ultralong wave! ) transmitter of genuine ( i.e. best-known-pov ) blox, would be a fine thing

asciilifeform: buncha monkeys, sitting on remnants of massive imperial machinery made by men. and looking for any, any way to leverage'em into a few moar yrs of pushing back the inevitable

asciilifeform: d00dz seem to be physically incapable of grasping a point by induction ( even the skyscrapers , apparently, didn't help... )

asciilifeform: gotta show ability for sustained extermination.

asciilifeform: ( they have constellation )

asciilifeform: gotta point out that nailing 1 enemy sat is not enough

asciilifeform: http://archive.is/264y7 << relatedly

asciilifeform: sorta why the balloon thing keeps coming back -- search for a midpoint b/w 'tower' and 'satellite' cost

asciilifeform: ( http://www.loper-os.org/wp-content/sultan.jpg oblig )

asciilifeform: mircea_popescu: 'cossacks write letter to the sultan' in order?

asciilifeform: less, incidentally, conspicuous, than monster flare from the ground

asciilifeform: but at any rate this is not open problem, it was solved in ~same way in all 3 major inca empires -- fighter goes to max altitude, launches slightly modified radar-seeker rocket, vertically.