46200+ entries in 0.031s
mircea_popescu: var selectedTextBox = (TextBox)sender, if (IsAdmin) { selectedTextBox.Enabled =
true; selectedTextBox.Text = superSecretPassword; } else{ selectedTextBox.Clear();}
mircea_popescu: asciilifeform how's it
to have
timeout if it doesn't know
time ?
mircea_popescu: and so on,
this constant up AND DOWN
the
tree calling paradigm recreates c++, java and usg necessarily.
mircea_popescu: see, cuz
things flow a certain way. "we want
to include morons, retards and other bureaucrats" --therefore--> "smartphones" and "ntp" and so on.
mircea_popescu: the issue of having every god damn peripheral aware of
time is another fucking bojum
mircea_popescu: (yes,
the objection stands, "mp, ada machjine long way off because all peripherals are c-machines". sure,
they are. we also make items.)
mircea_popescu: asciilifeform but
then i gotta what, write my own drivers/kernel mods for every peripheral ?
mircea_popescu: but in any case one can't have an ada machine without working abort (which specifically means, NOT import
the c consrtruct, cuz wtf am i gonna do.)
mircea_popescu: ie,
two layers are needed
to implement
the citizen/foreigner distinction.
mircea_popescu: seems
to me self-evident
that
there's need for exactly
two layers of exception handler : a) our code fucked up, in which case end it all or else b) some ~item~ such as whatever, a fg fucked up, in which case REPORT
THIS
TO ME, don't wait for it forever./
mircea_popescu: because in
truth, abort is
the wrong solution in 999 cases out of 1k
a111: Logged on 2016-01-21 13:29 asciilifeform: 'if i make it what i
think is
the right size, it crashes!111'
mircea_popescu: it's not clear
that
the complex exception handling mechanism with propagations and whatnot
that eventually yielded
the "try/catch" mechanism exposed in fucking code is ~at all useful~.
mircea_popescu: not all archs work well for
this, and evidently not all implementations are fucking useful.
mircea_popescu: diana_coman in ~principle~ zero cost exception handling is
this
thing : ~instead~ of calling code when exceptions arise, you instead unroll all calls in place, where exceptions might arise.
this way you don't get a run-time penalty (because you paid for it in code space)
diana_coman: mircea_popescu, so up
to v,
that's clear enough, lol
mircea_popescu: the most valuable (from a
timing perspective) loops are
the innermost ones, because
they get jumped in and out of hundreds of
tyimes.
diana_coman: that one might not care about
that or
the other maybe but
that doesn't mean it dun' exist now
diana_coman: asciilifeform, yes; my point was simply
that
their "zero-cost" is in fact all sorts of costs
diana_coman: also re zero-cost: "this method has considerably poorer performance for
the propagation of exceptions"
diana_coman: not a big deal; reading here on
the sjlj
theoretically
the biggest slowdown would be when
there are some exception handlers so maybe I should add
that
to
testing
diana_coman: so far yes because it's already at 0.46 secs; do you want it up
to k or what?
diana_coman will let it run some 1k
times and see an avg
mircea_popescu: the design calls for 20 loops each spawned by an if-even
test.
mircea_popescu: i wanted something in
there of a little heft
to make sure we're not being optimized or w/e.
a111: Logged on 2019-02-12 14:05 diana_coman: mircea_popescu, eucrypt's
test on Serpent seem good candidates as one can even adjust how many iterations
to do if you want some specific
time intervals; current full
test of
the serpent module (including i/o because of using
test vectors in file) is reported by
time at ~2.3s without sjlj;
this has no
tasks/exceptions as such;thing is:
time is not extremely precise but I could run I suppose some 1k
times and see
mircea_popescu: well, someone else gets
to rage in
the logs for a while.
mircea_popescu: yeah but i have nfi what it shits into
the obj code, and so on. but not off
the
table, no.
mircea_popescu: i guess,
though i am not sure
the correct approach is adding packages.
mircea_popescu: and fixing means ~have it handle all sigs~ wtf bs half-job is
this.
mircea_popescu: anyway, it's fucking insulting as all hell,
this zcx implementation. i suspect we will have
to fix it anyway, because it is not really feasible
to NOT have one, on irons
that support it.
mircea_popescu: exactly what i had in mind for "hey diana_coman check
this" if you returned
true.
a111: Logged on 2019-02-10 17:37 asciilifeform: will add
to
this also,
that if yer
thread is actually wedged, it will almost always be on acct of
http://btcbase.org/log/2019-02-08#1893811 , i.e. waiting for a blocking unix i/o, and no matter what yer pthreads proggy is written in , c, ada, cobol, whatever, it will still become a zombie, cuz unix is retarded.
diana_coman: certainly, but I'm kind of suspicious
that it actually works anyway
mircea_popescu: nah, we need
to
test
this properly, with a macroscopically blocking item
diana_coman: so hm, if you have a put_line and
then
the infinite loop, does
that still work?
diana_coman: asciilifeform, it works aka you checked
that it was *blocked* on
that i/o when it got aborted?
mircea_popescu: problem is you can't put a delay 0 ~inside~
the only
thing we fear, which is unix peripheral calls.
mircea_popescu: enjoy our zero cost health services from
the confort of your own home!
mircea_popescu: ima brb make some zero cost public services. like
the zero cost garbage pickup, and
the zero cost hospital, and so on.
mircea_popescu: this is what i was coming
to : do you have a better approach
to evaluating
the putative sjlj runtime cost
than
the above
thing diana's implementing nao ?
a111: Logged on 2019-02-12 13:18 bvt: i expect it will be slower, but it won't hurt
to do
the check.
the impact will depend on how exceptions are used (i don't
think it can have any impact on ffa, for example). but i don't have enough experience with it
to provide any numbers