asciilifeform: it , if one is to believe the docs, implements the '83 standard.
asciilifeform: phunphakt: in ye olde bolixtron, there is an ada ( and fortran! ) compiler. (however asciilifeform has not tried either item, beyond 'hello world' )
asciilifeform: 'new shithouse is built from the rubble of the old, not imported brick' or how did lenin put it.
asciilifeform: i have even moar wtf items in my collection.
asciilifeform: the world of the folx who wrote ada for moneys in the saeculum, is not , as i gather, a happy place. sorta why asciilifeform had to learn buncha things from 1st principles, rather than by reading their ugh
asciilifeform: ( observe, the only 'access pointer' in ffa is where it sucks in cmdline args from unix )
asciilifeform: mircea_popescu: sorta why i suspect 'greybeard'. prolly he also had a 200kloc (or 2e6...) that had to be dealt with as-is, pointerola & all.
asciilifeform: i suspect he was 'old guard' (ada greybeard) and the bottle took its toll.
asciilifeform: incidentally i cant think of any reason it wouldn't work exactly same with mysql, with the exception of where i dun yet know how to do the o(n log n) indices in mysql
asciilifeform: ( phuctor connects to a local instance of postgres, so in that sense similar )
asciilifeform: BingoBoingo: hey, if microshit can have weev jailed for munging URLs, why not acade-microshit and some other d00d , similarly
asciilifeform: cuz in the vice-versa variant, what you'll have is ~two~ threading systems that dun know about one another, and the shit one (cpp) doesn't have any concept of sane locks etc
asciilifeform: diana_coman: i suspect that even if you get the thing to properly link, you will discover new headaches on acct of http://btcbase.org/log/2019-01-06#1885177 . really imho proggy that has ada tasks oughta have ada main , and (if must) call static cpp turdola, not vice-versa☝︎
asciilifeform: last night i re-read diana_coman's piece on m-r , it is interesting just how much sweat diana_coman had to put in simply on account of koch gnarl☟︎
asciilifeform: or do i misread, and mod6 already reground, and writing re how.
asciilifeform: trb has , what, 3x the # of patches, so it'll take you 30m at most.
asciilifeform: mod6: at the risk of sounding like mircea_popescu in earlier thread -- why is this a mega-project ? i reground ffa to keccak in about 10minute (after getting hold of a working keccak-vtron)
asciilifeform: i'ma come back to this binomial once i have the m-r.
asciilifeform: grr, moar complicated than i initially pictured, because m-r ~also~ demands rng
asciilifeform: so depending on how many m-r shots you want, it can make sense to pre-sieve, to give m-r moar shots.
asciilifeform: the interesting thing about m-r however, is that it can make use of any available cpu given to it, to produce smaller probability of death
asciilifeform: i dun have the m-r yet, so cannot give the equation quite yet.
asciilifeform: ( and that on iron where m-r ends up taking substantially less time than FG takes to fill up candidate reg, there may not be a point to pre-sieving )
asciilifeform: my observation was that on a box with 1 FG, the latter will almost certainly be the limiting reactant in prime-baking.
asciilifeform: ( afaik there are no integers that are divisible by small prime (such as will fit in the primorial) and fail ~any~ number of m-r shots.
asciilifeform: cuz in the former case, there aint actually any point to gcd.
asciilifeform: nao, philosophical q : does one actually want to gcd + m-r always ? or is it acceptable to reject input after failed gcd litmus, and only ~then~ m-r .
asciilifeform: ( all of this assumes that nothing is parallelized. asciilifeform in particular does not like parallelized subcomponents in rsatron, if it can be avoided , tho there aint anyffin wrong with running ~multiple~ rsatrons , on diff inputs, in parallel , if iron is available )
asciilifeform: on a machine with multiple FG harnessed together, divide the figure by the # of FG in use.
asciilifeform: if primality test ( which consists of GCD ~and~ m-r, in order to constant-time ) does not exceed 0.0356sec, then on machine with 1 FG it can be considered that the FG is the limiting reactant.
asciilifeform: let's say yer baking one of the p, q of a 4096bit rsa mod. it needs 2048bit , i.e. 256byte of FG. a standard FG at room temp shits out 7kByte/s. therefore 256 / (7 x 1024) ~= 0.0357 sec., for a fillup of candidate register.
asciilifeform: on a box with 1 FG, the wait for a random fillup of a e.g. 2048bit reg, i suspect dwarfs the runtime of stein (and possibly even of m-r, dunno yet)