8300+ entries in 0.014s
mod6: Y(Y'First .. Y'First + K - 1),
mod6: Mul_Karatsuba(X(X'First .. X'First + K - 1),
mod6: Mul_Karatsuba(X0, Y0, P);
mod6: basically, being able to call something like:
mod6: just wondering if it could be a mechanical push, yet slightly more readable. maybe making 2^n version more grokable?
mod6: asciilifeform: so if you add back in the FZs that were removed in the 2^n version (re-adding in the 50% reduction of temp space that yields no opt.), do we get the ~runtime of the original?
mod6: <+asciilifeform> this kind of optimization could be interesting if we were dealing in MB+ ffaism << yeah, perhaps the sample size used was not enough to see the delta?
mod6: this is very interesting.
mod6: that's what i was trying to get at. i suppose the compiler would just reject your request to inline then, or perhaps thats ctronic thinking.
mod6: yeah, ok, so the compiler can't determine the max depth to unroll when recursive
mod6: this might be extra-strength dumb, but... in your new power of 2 version, do you need to inline the Mul & Square of karatsuba?
mod6: my ffa must be way old
mod6: but i've only scanned it once. so perhaps I shouldnt comment too much on that.
mod6: as it stands, at the moment, sounds like a mechanical push. with the ability to set the length to some power of two. i'd say it's a bit harder to follow, code-wise, with the recursive calls perhaps.
mod6: so you didn't get the 10%?
mod6: Guest41016 [~a111@unaffiliated/phf/bot/a111-]
mod6: phf: fwiw, i don't see a111 in my current /names list.
mod6: heheh, good to hear, Sir.
mod6: cool, let us know how it goes. :]
mod6: feel free to ask any questions.
mod6: <+mike_c> mod6 - you mentioned I might need some hand holding. anything I need to know that's not in
http://thebitcoin.foundation/trb-howto.html ? << that /should/ be all you need to know. less steps in the on-line version, but use which ever you need.
mod6: there was a bug that was discovered like a year ago
mod6: all my test results and stuff are posted
mod6: mike_c: i had quite a bit of fun testing those FGs; worked pretty great for me.
mod6: mircea_popescu: ah, ok. couldn't recall.
mod6: It's an ongoing project. The tickets are above, kinda outlines the idea ^
mod6: Unified Computing Interface
mod6: is there a trilema post on UCI?
mod6: ah yah, Mr. P. created his own hash function
mod6: i think, for the most part, it took me like ~8-12 weeks to get the hang of it.
mod6: it's actually not too bad.. just uber strict.
mod6: i've had to learn ada just to keep up & read the thing. help test where I can.
mod6: it's pretty amazing, really.
mod6: <+mircea_popescu> mike_c but look at the new v-based trb build << yah, if you're interested in standing up a node, we'll talk ya through it.
mod6: you're were starting to enter vrag territory.
mod6: i've been optimistic though; know you've been busy. don't hesitate to drop us a line tho!
mod6: how ya been mike_c ?
mod6: mike_c: it's now ``!!up'' and ``!!v <OTP>''
mod6: deedbot might have added the second '!' since then.
mod6: edivad: yah, it'll really help you out to read at least 6 months of logs. And if you read more, even better. There's a wealth of knowledge in there.
mod6: I'll say 20G, that should suffice, for now.
mod6: yeah, that's always what mine is once complete, ~4.5G
☟︎ mod6: <+trinque> ah well sure, suppose mod6 could mention the build environment is going to be big. << While I'm at it on the updates; i think, let's say, you need a minimum of what? 20Gb ?
mod6: <+edivad> i was doing the process in a 8gb container and at a point i wasn't so confortable continuing refreshing df to check my free space << oh sure. I didn't even think to ask. Next time I will.
mod6: <+edivad> thanks again to all of you that have helped me in the troubleshooting << You're welcome. Very good of you to have such persistence to keep working through the issues.
mod6: <+edivad> i have a super good news, node is compiled, up and running << yay!
mod6: edivad: if `locate` doesn't find it, perhaps a simple find will: `find / -name "CheckIncludeFiles.cmake"`
mod6: <+shinohai> mircea_popescu: The cmake in Debian/Ubuntu repositories used to have that pthread bug, first time I built a trb with `V` that happened. << i don't remember ever having this issue fwiw
mod6: ok good to denote. thanks. let us know if it all builds fine for ya.
mod6: and when you say 'mint' you don't mean 'linux mint' right? just a *new/clean* ubuntu sys?
mod6: strange, im not sure what you mean.
mod6: ok, that /is/ a bit less steps, so a decent place to start until you get the hang of the process.
mod6: edivad: are you doing the online or offline build?
mod6: i would blow everything away and start over following exact instructions in the howto
mod6: im not sure. digging...
mod6: yeah, this looks like it might be something with your /etc/alternatives or something
mod6: did everything press alright with V ?
mod6: yeah, it does not seem to understand where 'c' is located.
mod6: Ok, I think it's better now.
mod6: ugh, something went sideways, standby
mod6: Updated the formatting too.
mod6: But wouldn't be a bad idea to throw it on there in the case where someone, decides to use the linked vdiff script, which uses diff.
☟︎ mod6: my V doesn't use diff anyway, only patch, gpg, sha512sum, and wget -- and otherwise just standard shell tools such as echo, mkdir, rm, cat, etc.