fche changed the topic of #systemtap to: http://sourceware.org/systemtap; email systemtap@sourceware.org if answers here not timely, conversations may be logged
orivej has joined #systemtap
<agentzh>
yay! we've just got soft float working in our own stap branch :D
<agentzh>
simple literals and printing are now working.
<agentzh>
arithmetic should be easy too, we just haven't exposed the tapset functions yet. but the code is already there and the printf() function already uses the float-num arithmetic a bit.
<agentzh>
i can commit it once you greenlight it :)
<fche>
agentzh, looks good, thanks
slowfranklin has joined #systemtap
<agentzh>
fche: great, i'll commit it then :)
<agentzh>
btw, the tests were generated from our declarative test cases by my own tool :)
<agentzh>
spent a couple of days learning tcl and expect.
<fche>
hope the scars will heal :)
<agentzh>
heh
<agentzh>
the most tricky part is to convert perl regexes to tcl ones.
<agentzh>
the latter has some tricky differences.
<fche>
yeah, and expect adds some of its own
<agentzh>
another tricky thing is tcl's quoting rules.
<agentzh>
even [ and { are special.
<agentzh>
*nod*
<fche>
wrapping things in {} is the safest bet
<agentzh>
yeah, but {...} has its own peculiarities.
<agentzh>
like it does not allow unbalanced `{` and `}`.
<agentzh>
and escaping won't work there.
<fche>
it won't parse within {} except for } itself
<fche>
so {.*"foo[]bar} is fine
<agentzh>
yeah, but not {{} or {}}.
<fche>
yup, nested {} need to be quoted, but that's it
<fche>
tcl rules are not too tricky
<agentzh>
aye, just need some time to get used to.
<fche>
yup
<agentzh>
oh, btw, is there a way to speed up running a single test file?
<agentzh>
i don't mind if it is dirty.
<fche>
what do you mean speed up ... single?
<agentzh>
right now it spends a lot of time checking gcc and running some environment.exp
<fche>
just run one test?
<agentzh>
yes
<agentzh>
that is hurting.
<fche>
ah - it does some smoke-testing of the environment early on
<agentzh>
i'm using sudo make -j2 installcheck-parallel RUNTESTFLAGS= TESTS='*/at_var_print.exp'
<agentzh>
but it spends more than half of the time doing setup work.
<agentzh>
that's very inefficient for me :)
<agentzh>
so wondering if the setup work can be either cached or skipped with some hacks even.
<agentzh>
or if you have some other trick for everyday development.
<fche>
I usually just suffer the, what, ten seconds
slowfranklin has quit [Quit: slowfranklin]
slowfranklin has joined #systemtap
<agentzh>
fche: oy
<agentzh>
it's 20 sec on my side ;)
<agentzh>
just measured it.
<agentzh>
fche: just committed that patch to master.
<fche>
thanks
slowfranklin has quit [Quit: slowfranklin]
<agentzh>
fche: sure. many more are coming :)
<agentzh>
fche: one quick question, what does the _p suffix stand for in stap's variable/command names? it looks like some kind of flag or boolean indicator, but not sure about the actual p* word.