sb0 changed the topic of #m-labs to: ARTIQ, Migen, MiSoC, Mixxeo & other M-Labs projects :: fka #milkymist :: Logs http://irclog.whitequark.org/m-labs
tangrs has left #m-labs ["Leaving"]
d_n|a has quit [Ping timeout: 248 seconds]
<_florent_> rjo: thanks for the cordic, I'll integrate that today
FabM has joined #m-labs
<sb0> bb-m-labs_, force build --branch=rtio-sed artiq
<bb-m-labs_> build forced [ETA 34m35s]
<bb-m-labs_> I'll give a shout when the build finishes
<GitHub199> [artiq] sbourdeauducq pushed 1 new commit to rtio-sed: https://github.com/m-labs/artiq/commit/5437f0e3e36cabce5757b343db7d3b2a5bb5fbde
<GitHub199> artiq/rtio-sed 5437f0e Sebastien Bourdeauducq: rtio: make sequence errors consistently asychronous
<rjo> sb0: do you want to check the mods from sinara#327?
<rjo> sb0: yes. imho we can forego the RCs. feel free to go ahead and release 3.0
<sb0> well it didn't work on the board we had in the US either
<sb0> the last comments could explain why the media converter doesn't find a link with the HK boards though. i'll take a look.
<sb0> hmm but didn't Greg say this chip was doing rate conversion?
<sb0> with the SFP side always at 1G
<bb-m-labs_> build #788 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/788
<sb0> also my instruction for ethernet was "copy the kc705 schematics". if Joe and Greg had followed this, and disconnected the mmc, this mess would not exist.
<sb0> and I suggested that after Joe said he did not want to pay for more Ethernet work. we should also have him revise that position.
<bb-m-labs_> build #1688 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1688
<sb0> okay, I'll finish some rtio work (report channel number on async error) then release 3.0 with or without #830
<rjo> the kc705 schematics would not have worked with the crate backplane. that's why the chip was changed. iirc you were there when that was discussed.
<rjo> ack.
<sb0> I wasn't happy about in-crate ethernet either
<sb0> bb-m-labs_, force build --branch=rtio-sed artiq
<bb-m-labs_> build forced [ETA 34m35s]
<bb-m-labs_> I'll give a shout when the build finishes
<GitHub16> [artiq] sbourdeauducq pushed 1 new commit to rtio-sed: https://github.com/m-labs/artiq/commit/6c049ad40ccf172137a76a8b8ae843fc0ab282b7
<GitHub16> artiq/rtio-sed 6c049ad Sebastien Bourdeauducq: rtio: report channel numbers in asynchronous errors
<GitHub177> [migen] sbourdeauducq tagged 0.5 at master: https://git.io/vd35g
<sb0> bb-m-labs_, force build migen
<bb-m-labs_> build forced [ETA 3m26s]
<bb-m-labs_> I'll give a shout when the build finishes
<GitHub47> [misoc] sbourdeauducq tagged 0.6 at master: https://git.io/vd35P
<sb0> bb-m-labs_, force build misoc
<bb-m-labs_> The build has been queued, I'll give a shout when it starts
<bb-m-labs_> build #190 of migen is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/migen/builds/190
<bb-m-labs_> build forced [ETA 2m51s]
<bb-m-labs_> I'll give a shout when the build finishes
<bb-m-labs_> build #251 of misoc is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/251
<GitHub37> [artiq] sbourdeauducq pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/c00b3fe8cd4c...071439f9bdcd
<GitHub37> artiq/master 6d72329 Sebastien Bourdeauducq: RELEASE_NOTES: 3.0
<GitHub37> artiq/master 071439f Sebastien Bourdeauducq: conda: use migen/misoc releases
<sb0> bb-m-labs_, force build misoc
<bb-m-labs_> build forced [ETA 2m51s]
<bb-m-labs_> I'll give a shout when the build finishes
<bb-m-labs_> build #252 of misoc is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/252
<GitHub> [conda-recipes] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/conda-recipes/commit/44bda1de22eb81f1ad1b6d7bd1dcc56fe52d0c60
<GitHub> conda-recipes/master 44bda1d Sébastien Bourdeauducq: llvmlite-artiq: remove .dev from version number...
<sb0> bb-m-labs: force build --props=package=llvmlite-artiq conda-all
<sb0> rjo, should artiq 3.0 use jesd204b 0.3 or 0.4?
<bb-m-labs_> build #789 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/789
<rjo> sb0: 0.3 is fine.
<sb0> bb-m-labs, force build --props=package=llvmlite-artiq conda-all
<sb0> bb-m-labs_, force build --props=package=llvmlite-artiq conda-all
<bb-m-labs_> build #89 forced
<bb-m-labs_> I'll give a shout when the build finishes
<bb-m-labs_> build #174 of conda-win32 is complete: Failure [failed conda_clean_lock] Build details are at http://buildbot.m-labs.hk/builders/conda-win32/builds/174
<bb-m-labs_> build #177 of conda-win64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/177
<bb-m-labs_> build #328 of conda-lin64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-lin64/builds/328
<bb-m-labs_> build #89 of conda-all is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/conda-all/builds/89
<sb0> is there any release that doesn't involve working around a dozen conda bugs?
<bb-m-labs_> build #1689 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1689
<sb0> ah wow, conda on win32 is really fucked, I cannot even run the activate script
<sb0> bb-m-labs_, force build --props=package=llvmlite-artiq conda-win64
<bb-m-labs_> build #178 forced
<bb-m-labs_> I'll give a shout when the build finishes
<bb-m-labs_> build #178 of conda-win64 is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/178
<bb-m-labs_> build #790 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/790
<sb0> who is still using win32?
<sb0> bb-m-labs_, force build --props=package=llvmlite-artiq conda-win64
<bb-m-labs_> The build has been queued, I'll give a shout when it starts
<sb0> well basically it seems that python 3.5 with conda is hosed on win32
<bb-m-labs_> build #573 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/573
<bb-m-labs_> build #179 forced
<bb-m-labs_> I'll give a shout when the build finishes
<bb-m-labs_> build #1690 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1690
<rjo> sb0: that was only the old nist machines due to a compat issue. ping daniel and then stop shipping 32 bit precompiled packages.
<bb-m-labs_> build #179 of conda-win64 is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/conda-win64/builds/179
<rjo> _florent_: thenks the updates. if you have given it a quick test, could you drill greg and instruct him how to use it? probably good to note that this thing runs at 125 MHz, un-interpolated, and that max amplitude is 0x4db9.
<rjo> _florent_: from the code is looks like there is only two-fold sample repotition, i.e. 250MHz sample rate. is that correct? aren't you using 10 Gbit/s, 1000 MHz sample rate?
<rjo> _florent_: thanks for posting the bitstreams. i'll write that instruction. but what's the actual fabric frequency of the cordic and why does it not repeat each sample 1000 MHz/125 MHz = 8 times?
attie has quit [Remote host closed the connection]
attie has joined #m-labs
d_n|a has joined #m-labs
<d_n|a> whitequark/sb0: What's the holdup with #830?
<sb0> whitequark, ^
<GitHub196> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/74dbb4c977fd07c9933c6ceed490ae5c24f79b50
<GitHub196> artiq/master 74dbb4c Sebastien Bourdeauducq: conda: use non-dev llvmlite-artiq
<d_n|a> (I.e. just generate the obvious code using a conditional for now, and worry about optimizing it beyond what LLVM does later)
<bb-m-labs_> build #791 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/791
<bb-m-labs_> build #574 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/574
<bb-m-labs_> build #1691 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1691
d_n|a has quit [Ping timeout: 240 seconds]
<sb0> bb-m-labs: force build --props=package=artiq-kc705-nist_qc2 artiq-board
halfr is now known as halfr_
halfr_ is now known as halfr1
<GitHub13> [artiq] sbourdeauducq created release-3 (+1 new commit): https://github.com/m-labs/artiq/commit/ac28b377c7d3
<GitHub13> artiq/release-3 ac28b37 Sebastien Bourdeauducq: targets: phaser → kc705_phaser
<sb0> bb-m-labs: force build --props=package=artiq-kc705-phaser --branch=release-3 artiq-board
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-nist_qc2 artiq-board
<bb-m-labs_> build forced [ETA 13m00s]
<bb-m-labs_> I'll give a shout when the build finishes
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-phaser --branch=release-3 artiq-board
<bb-m-labs_> The build has been queued, I'll give a shout when it starts
<sb0> rjo, do we keep artiq/gateware/targets/kc705_sma_spi.py?
<rjo> sb0: let's keep it. i use it.
<sb0> what major features should we announce? DMA? PDQ2? DRTIO and SAWG demos?
<bb-m-labs_> build #792 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/792
<bb-m-labs_> build forced [ETA 14m48s]
<bb-m-labs_> I'll give a shout when the build finishes
<bb-m-labs_> build #793 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/793
<GitHub85> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/04a9a0ce95947185a8fb38f886e515ab239e544d
<GitHub85> artiq/release-3 04a9a0c Sebastien Bourdeauducq: doc: no more win32 packages
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-nist-qc2 --branch=release-3 artiq-board
<bb-m-labs_> build forced [ETA 14m48s]
<bb-m-labs_> I'll give a shout when the build finishes
<bb-m-labs_> build #794 of artiq-board is complete: Failure [failed get_output_name] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/794
<sb0> bb-m-labs_: force build --branch=release-3 artiq
<bb-m-labs_> build forced [ETA 36m16s]
<bb-m-labs_> I'll give a shout when the build finishes
d_n|a has joined #m-labs
d_n|a has quit [Ping timeout: 258 seconds]
<rjo> sb0: in no particular order: DMA, DRTIO, SAWG, out-of-tree PDQ, rust, smoltcp
<bb-m-labs_> build #795 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/795
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-nist-qc2 --branch=release-3 artiq-board
<bb-m-labs_> build forced [ETA 13m38s]
<bb-m-labs_> I'll give a shout when the build finishes
d_n|a has joined #m-labs
<bb-m-labs_> build #796 of artiq-board is complete: Failure [failed get_output_name] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/796
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-phaser --branch=release-3 artiq-board
<bb-m-labs_> build forced [ETA 13m38s]
<bb-m-labs_> I'll give a shout when the build finishes
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs_> The build has been queued, I'll give a shout when it starts
<bb-m-labs_> build #797 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/797
<bb-m-labs_> build forced [ETA 16m23s]
<bb-m-labs_> I'll give a shout when the build finishes
gric has quit [Ping timeout: 260 seconds]
gric has joined #m-labs
<bb-m-labs_> build #575 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/575
<bb-m-labs_> build #1692 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1692
<whitequark> sb0: no holdup. I tried to understand it yesterday properly but couldn't quite, let me just copy the code
<bb-m-labs_> build #798 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/798
<sb0> bb-m-labs_: force build --branch=release-3 artiq
<bb-m-labs_> build forced [ETA 43m50s]
<bb-m-labs_> I'll give a shout when the build finishes
<GitHub1> [artiq] sbourdeauducq tagged 3.0 at 3b88eba: https://github.com/m-labs/artiq/commits/3.0
d_n|a has quit [Ping timeout: 248 seconds]
<bb-m-labs_> build #1693 of artiq is complete: Failure [failed python_unittest] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1693
<sb0> wtf
<sb0> bb-m-labs_: force build --branch=release-3 artiq
<bb-m-labs_> build forced [ETA 43m50s]
<bb-m-labs_> I'll give a shout when the build finishes
<rjo> whitequark, sb0: should we hook up the machine here in berlin as a buildslave?
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs_> The build has been queued, I'll give a shout when it starts
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-phaser --branch=release-3 artiq-board
<bb-m-labs_> The build has been queued, I'll give a shout when it starts
<GitHub103> [artiq] sbourdeauducq tagged 4.0.dev at e7594b5: https://github.com/m-labs/artiq/commit/e7594b540ee0
<GitHub103> artiq/4.0.dev e7594b5 Sebastien Bourdeauducq: RELEASE_NOTES: add 4.0 section
<GitHub196> [artiq] sbourdeauducq pushed 2 new commits to master: https://github.com/m-labs/artiq/compare/74dbb4c977fd...c7cdd2016ac6
<GitHub196> artiq/master e7594b5 Sebastien Bourdeauducq: RELEASE_NOTES: add 4.0 section
<GitHub196> artiq/master c7cdd20 Sebastien Bourdeauducq: doc: no more win32 packages
<sb0> rjo, to the main buildbot?
<rjo> sb0: yes
<whitequark> rjo: what's the benefit?
<whitequark> or rather, the purpose?
<rjo> dunno. that's why i'm asking. do we need more cpu/mem/kc705s?
<sb0> mem/kc705 no, cpu not sure
<bb-m-labs_> build #799 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/799
<bb-m-labs_> build forced [ETA 14m35s]
<bb-m-labs_> I'll give a shout when the build finishes
<bb-m-labs_> build #1694 of artiq is complete: Failure [failed conda_install] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1694
<sb0> conda/builbot is again a trash fire ...
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-nist_clock --branch=release-3 artiq-board
<bb-m-labs_> The build has been queued, I'll give a shout when it starts
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs_> The build has been queued, I'll give a shout when it starts
<GitHub47> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/4bafdecd47950fdb9eae4dd9b7c0f050a575a3c7
<GitHub47> artiq/master 4bafdec Sebastien Bourdeauducq: RELEASE_NOTES: formatting
<GitHub31> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/d500e61d89f449d8c2eff2d2b66d0ca7bcb97f04
<GitHub31> artiq/release-3 d500e61 Sebastien Bourdeauducq: RELEASE_NOTES: formatting
<GitHub23> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/b4c52c34f7e022a90a31b13303a182d2c7ac3717
<GitHub23> artiq/master b4c52c3 Sebastien Bourdeauducq: Merge branch 'sinara'
<GitHub16> [artiq] sbourdeauducq deleted sinara at 38388d1: https://github.com/m-labs/artiq/commit/38388d1
<whitequark> sb0: more ram is always good as it lets us use vms more widely
<sb0> i'll merge rtio-sed later, since it has sawg/sayma breakage potential
<whitequark> e.g. we could move all builds to checkpointed vms
<whitequark> that's 1-2 days of fixing buildbot config and it gives us completely repeatable builds sans intrinsic things like embedded timestamps
<sb0> we have 16GB RAM now. is that not enough for doing that already?
<whitequark> barely
<whitequark> vivado needs how much?
<whitequark> well, we could limit parallel vivado builds, and use ballooning
<bb-m-labs_> build #800 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/800
<bb-m-labs_> build forced [ETA 18m30s]
<bb-m-labs_> I'll give a shout when the build finishes
<_florent_> rjo: indeed there is something wrong, I should have fix converter datas, but cordic is running at 250Mhz, can you give the new csr parameters if differents?
<bb-m-labs_> build #801 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/801
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-nist_qc2 --branch=release-3 artiq-board
<bb-m-labs_> The build has been queued, I'll give a shout when it starts
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-nist_qc2 --revision=04a9a0ce95947185a8fb38f886e515ab239e544d artiq-board
<bb-m-labs_> The build has been queued, I'll give a shout when it starts
<GitHub88> [artiq] sbourdeauducq pushed 1 new commit to release-3: https://github.com/m-labs/artiq/commit/a49bb2bc50f3294ce4a9ae177aa7789954b3bc88
<GitHub88> artiq/release-3 a49bb2b Sebastien Bourdeauducq: conda: fix llvmlite-artiq dependency
<GitHub152> [artiq] sbourdeauducq pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/0f4bc54e920ca9ddcde0a8a9969a37d4d9f659f3
<GitHub152> artiq/master 0f4bc54 Sebastien Bourdeauducq: conda: fix llvmlite-artiq dependency
<rjo> _florent_: but if the cordic runs at 250MHz, then you still need to repeat every sample 4 times (not 2).
<bb-m-labs_> build #802 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/802
<bb-m-labs_> build forced [ETA 15m34s]
<bb-m-labs_> I'll give a shout when the build finishes
<_florent_> rjo: yes i changed that
<rjo> if the cordic runs at 250MHz (assuming it meets timing) then the frequency is just twice the value, i.e. 20 MHz.
<_florent_> ok
<_florent_> rjo: ok thanks, i uploaded the new bitstreams
d_n|a has joined #m-labs
<bb-m-labs_> build #803 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/803
<bb-m-labs_> build forced [ETA 15m34s]
<bb-m-labs_> I'll give a shout when the build finishes
<sb0> bb-m-labs_: force build --props=package=artiq-kc705-nist_clock --revision=04a9a0ce95947185a8fb38f886e515ab239e544d artiq-board
<bb-m-labs_> The build has been queued, I'll give a shout when it starts
<rjo> _florent_: i updated the comment.
<rjo> _florent_: thanks for integrating that!
<rjo> _florent_: would you do me a favor with your sayma? if you have a linux machine (a bit easier with linux than with windows but it should also work just fine on windows), could you try our openocd branch and the proxy bitstream on your sayma and see whether the second flash chip works?
<_florent_> rjo: i'll try to test that next week
<bb-m-labs_> build #804 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/804
<bb-m-labs_> build forced [ETA 16m17s]
<bb-m-labs_> I'll give a shout when the build finishes
<rjo> _florent_: merci!
FabM has quit [Quit: ChatZilla 0.9.93 [Firefox 52.3.0/20170811091919]]
<_florent_> rjo: can you just give me the exact intructions to execute? (to avoid loosing time)
<bb-m-labs_> build #805 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/805
<bb-m-labs_> build #576 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/576
<bb-m-labs_> build #1695 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1695
d_n|a has quit [Ping timeout: 240 seconds]
<bb-m-labs_> build #806 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/806
rohitksingh has joined #m-labs
<bb-m-labs_> build #577 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/577
<bb-m-labs_> build #1696 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1696
<GitHub41> [artiq] jordens closed issue #800: jtag for sayma/ultrascale https://github.com/m-labs/artiq/issues/800
<GitHub61> [artiq] jordens pushed 5 new commits to master: https://github.com/m-labs/artiq/compare/0f4bc54e920c...c7de2332083b
<GitHub61> artiq/master 2821f50 Robert Jordens: conda: jesd204b 0.4
<GitHub61> artiq/master 2604806 Robert Jordens: sayma_rtm: make build dir
<GitHub61> artiq/master 5e3cc83 Robert Jordens: sayma_amc: SAWG (untested)
<bb-m-labs_> build #807 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/807
<bb-m-labs_> build #578 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/578
<bb-m-labs_> build #1697 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1697
<GitHub130> [artiq] cjbe opened issue #835: Compiler crash on list addition https://github.com/m-labs/artiq/issues/835
rohitksingh has quit [Quit: Leaving.]
<GitHub164> [artiq] cjbe opened issue #836: Compiler crash using unary operator https://github.com/m-labs/artiq/issues/836
d_n|a has joined #m-labs
<GitHub83> [artiq] whitequark commented on issue #836: I forgot to implement it. https://github.com/m-labs/artiq/issues/836#issuecomment-333260961