sb0_ changed the topic of #m-labs to: https://m-labs.hk :: Logs http://irclog.whitequark.org/m-labs
<bb-m-labs> build #2229 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2229
zoobab has quit [Ping timeout: 246 seconds]
zoobab has joined #m-labs
<d_n|a> rjo: Turns out it was a fairly subtle bug in the phase tracking code (or, arguably, the compiler): https://github.com/m-labs/artiq/commit/3e84ec2bf1d32e063dd22f59f65aef62a24c9911
<whitequark> d_n|a: it's intentional behavior
<d_n|a> Silently doing a lossy cast is? We should change those language semantics then.
<whitequark> yes, silently doing a lossy cast is intentional behavior
<whitequark> in the past i've pushed for overflow being an exception
<whitequark> sb0 decided that it won't happen
<d_n|a> Arithmetic overflow isn't the same as downcasting, though - or do you mean checking on downconversion?
<whitequark> yeah
<whitequark> all overflows, not just arithmetic overflows
<whitequark> or1k even has an overflow flag, but it has stupid useless semantics so we'd have to do an arch extension
<bb-m-labs> build #2230 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2230
<d_n|a> In either case, we should seriously reconsider the design here, though (silent lossy implicit conversion, that is).
<bb-m-labs> build #2813 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2813 blamelist: David Nadlinger <code@klickverbot.at>
<whitequark> sure
<d_n|a> The kind of close-to-hardware code that ARTIQ Python is mostly used for is especially prone to these errors, so the language semantics should be chosen appropriately
<d_n|a> Huh, is test_pulse_rate flakey again?
<whitequark> it should, but then it departs even further from being a subset of python
<whitequark> in my view, python is a completely wrong base language to use for this in the first place
<whitequark> it gives nothing but passing familiarity, and creates a lot of difficulties, e.g.: numbers, inheritance, ...
zoobab has quit [Ping timeout: 250 seconds]
zoobab has joined #m-labs
<bb-m-labs> build #2231 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2231
<bb-m-labs> build #2232 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2232
<bb-m-labs> build #2814 of artiq is complete: Failure [failed anaconda_upload_1 python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2814 blamelist: David Nadlinger <code@klickverbot.at>
kc5tja has joined #m-labs
<bb-m-labs> build #2233 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2233
<bb-m-labs> build #2234 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2234
<bb-m-labs> build #2815 of artiq is complete: Failure [failed make_doc python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2815 blamelist: Drew <drewrisinger@users.noreply.github.com>
monicaleung has quit [Quit: Leaving]
lkcl has quit [Excess Flood]
lkcl has joined #m-labs
futarisIRCcloud has joined #m-labs
_whitelogger has joined #m-labs
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 258 seconds]
rohitksingh has joined #m-labs
rohitksingh has quit [Ping timeout: 245 seconds]
rohitksingh has joined #m-labs
kc5tja has quit [Ping timeout: 250 seconds]
rohitksingh has quit [Ping timeout: 245 seconds]
rohitksingh has joined #m-labs
<sb0> whitequark: what do you propose?
<bb-m-labs> build #2235 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2235
<whitequark> sb0: for kernels? i would personally just program them in rust.
<whitequark> that would solve basically all of our language problems, except for RPC autogeneration.
<sb0> whitequark: you still have not explained why val isn't always 64-bit in #1242
<whitequark> le'sODODt see
<sb0> whitequark: as for ecp5, that's much lower priority than addressing the various long-standing issues that have been discussed before
<sb0> and satman optimization
<whitequark> hm, artiq is broken on python3.7
<whitequark> sb0: can you fix thorlabs_tcube/driver.py?
<whitequark> async is no longer a contextual keyword on 3.7
<whitequark> not sure what uses that file
<sb0> whitequark: there is no funding for py3.7 support. why do you need it?
<whitequark> debian's python3 is now 3.7 and i run debian.
<whitequark> well, feel free to ignore. i don't really care one way or another so long as the parts i need still work.
<whitequark> just thought it'd be easier to do this sooner.
<sb0> that's also what I keep telling people...
<whitequark> what do you tell? that it'd be easier to migrate sooner than later?
<sb0> yes, and that conda will end up (even more broken) if we stick to an old python
<whitequark> seems about right.
<bb-m-labs> build #2236 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2236
<bb-m-labs> build #988 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/988
<bb-m-labs> build #2816 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2816
<whitequark> sb0: so, the reason `val` ends up as int32 is the cast used in assignment to `val_lower_int32`
<whitequark> this is probably a bug in pass ordering.
<whitequark> unfortunately, while this specific instance (with the literal) is a bug, i can construct some very similar example that would still be broken, by making clever use of operators
<whitequark> replace it with 1<<32 and you'll have the same problem
<whitequark> which won't be fixed by the fix i'm about to apply
<bb-m-labs> build #2237 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2237
<bb-m-labs> build #2238 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2238
<bb-m-labs> build #989 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/989
<bb-m-labs> build #2817 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2817
<bb-m-labs> build #2239 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2239
<bb-m-labs> build #2240 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2240
<bb-m-labs> build #2818 of artiq is complete: Failure [failed python_unittest_3] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2818 blamelist: whitequark <whitequark@whitequark.org>, David Nadlinger <code@klickverbot.at>
dlrobertson has joined #m-labs
kc5tja has joined #m-labs
rohitksingh has quit [Ping timeout: 258 seconds]
<bb-m-labs> build #2241 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2241
<bb-m-labs> build #2242 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2242
<bb-m-labs> build #990 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/990
<bb-m-labs> build #2819 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2819
<bb-m-labs> build #2243 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2243
<bb-m-labs> build #2244 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2244
rohitksingh has joined #m-labs
<bb-m-labs> build #991 of artiq-win64-test is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/991
<bb-m-labs> build #2820 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2820
<d_n|a> bb-m-labs: force build --branch=pull/1244/merge artiq
<bb-m-labs> build forced [ETA 58m23s]
<bb-m-labs> I'll give a shout when the build finishes
<bb-m-labs> build #2245 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2245
X-Scale` has quit [Ping timeout: 244 seconds]
X-Scale has joined #m-labs
<bb-m-labs> build #2246 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/2246
<bb-m-labs> build #2821 of artiq is complete: Failure [failed python_unittest_2] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/2821
_whitelogger has joined #m-labs
kc5tja has quit [Ping timeout: 250 seconds]