<GitHub5>
artiq/master 6940d98 Robert Jordens: gitignore: minor tweaks, recommend /run for testbed
<GitHub5>
artiq/master 063e88d Robert Jordens: artiq/_version.py: update
<cr1901_modern>
Wasn't aware libm had a bessel function
<cr1901_modern>
Oh, that's b/c they're called j0, j1, etc, and I never bothered to make the connection lol
<whitequark>
rjo: they won't be in the runtime unless you actually use them
<whitequark>
feel free to take anything you find unneeded from our copy of libm, i just felt that if it calls itself libm it might as well be the whole deal
<rjo>
whitequark: sure. and they would need hooking up to APython as well.
<whitequark>
rjo: that is as simple as adding a syscall and then extending the export table in ksupport
<whitequark>
(we can actually get rid of it if desired, if we use the ELF tables in ksupport.elf...)
<rjo>
sb0, felix_: whatever you guys did to lwip/ppp/uart flood ping works fine now.
<GitHub116>
artiq/master cf17be9 Robert Jordens: doc: add artiq_flash
rohitksingh has quit [Ping timeout: 256 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 250 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
aeris has joined #m-labs
aeris has quit [Remote host closed the connection]
sb0 has joined #m-labs
<sb0>
rjo, I think creating a stable branch means more than tagging... we should also do some testing, backport bugfixes, etc.
<sb0>
it's quite some work. do you see cases where you'd tell people to keep using the old compiler?
<sb0>
afaict after the parallel implementation is sorted out, the new compiler should run all the (meagre) user code base.
<sb0>
i'd rather make your 2.0 the 1.0, and maintain that branch seriously
ylamarre has joined #m-labs
aeris has joined #m-labs
<sb0>
rjo, why did you create ppp2 instead of updating the existing branch?
<sb0>
rjo, why would you put the testbeds in-tree?
aeris has quit [Remote host closed the connection]
aeris has joined #m-labs
aeris has quit [Remote host closed the connection]
aeris has joined #m-labs
aeris has quit [Remote host closed the connection]
sb0 has quit [Quit: Leaving]
<rjo>
sb0: creating stables branches is just that: creating stable branches. if there is the need for it, bugfixes will need to be backported.
<rjo>
no. i don't see anybody using that 1.x right now. but that point is a pivotal nontheless.
<rjo>
i don't see a problem if the first version of artiq that takes paper-data is 2.0. and even that is just a humble wish so far.
<rjo>
there is also your 0.0
<rjo>
i created ppp2 because i rebased (was much easier) which would mean that history would get lost if i force-pushed that to ppp.
<rjo>
once you say there is nothing in your ppp branch anymore worth keeping, it can go
<rjo>
testing things in-tree is something that at least whitequark and i do all the time. we apparently don't like cd'ing around or adding lots of options to artiq_* cli tools.