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
ylamarre has quit [Quit: ylamarre]
<sb0> whitequark, dds_init works fine on master/kc705 here. i guess rjo tested it on the pipistrello as well
<sb0> shoud I try on pipistrello?
<whitequark> yes, I think so
<whitequark> I could not trace it to anything I could have broken
<sb0> are you trying master?
<whitequark> I think I tried master, yes
<GitHub101> [misoc] whitequark pushed 2 new commits to master: http://git.io/vOZTW
<GitHub101> misoc/master 36e03ec whitequark: libdyld: R_*_RELATIVE never specify a symbol.
<GitHub101> misoc/master b8a5568 whitequark: libdyld: handle existing but undefined symbols during lookup.
<GitHub151> [misoc] whitequark force-pushed master from b8a5568 to 6a1b0b3: http://git.io/LjONPA
<GitHub151> misoc/master 6a1b0b3 whitequark: libdyld: handle existing but undefined symbols during lookup.
<whitequark> phew, this nearly works
<whitequark> one unaligned access left...
<cr1901_modern> So that's what your question on twitter was about. Of course I missed the point of it.
<whitequark> YES
<whitequark> IndexError(index {0} out of bounds 0:{1}, 10, 1, 0)
<whitequark> it threw and caught an exception within Python code.
<whitequark> speaking of things that work, binutils. fucking piece of shit. i spent at least six hours chasing a s/TRUE/FALSE/ which was copy-pasted by whoever added the OR1K support
<whitequark> and it's not even some kind of tricky relocation. it's the most barebones possible one. but noooo
<GitHub174> [artiq] whitequark pushed 1 new commit to new-py2llvm: http://git.io/vOZL2
<GitHub174> artiq/new-py2llvm cd294e2 whitequark: artiq_personality: avoid unaligned loads.
<GitHub156> [artiq] whitequark pushed 1 new commit to new-py2llvm: http://git.io/vOZqJ
<GitHub156> artiq/new-py2llvm aae2923 whitequark: runtime: add lognonl{,_va} functions....
<GitHub183> [artiq] whitequark pushed 1 new commit to new-py2llvm: http://git.io/vOZqY
<GitHub183> artiq/new-py2llvm 6db93b3 whitequark: artiq_personality: port to device.
<GitHub83> [artiq] whitequark pushed 1 new commit to new-py2llvm: http://git.io/vOZmU
<GitHub83> artiq/new-py2llvm 122b3b0 whitequark: Integrate libdyld and libunwind....
travis-ci has joined #m-labs
<travis-ci> m-labs/artiq#351 (master - ebbbdcf : Robert Jordens): The build has errored.
travis-ci has left #m-labs [#m-labs]
<GitHub81> [misoc] sbourdeauducq pushed 1 new commit to master: http://git.io/vOZcO
<GitHub81> misoc/master b1445ae Sebastien Bourdeauducq: dyld: style
<sb0> cr1901_modern, there is still a lot of stuff in this minimal example. is every character strictly needed?
imrehg has joined #m-labs
<sb0> whitequark, common_init() returns fine here
<sb0> commenting it out should have no particular ill effects as you don't have DDSes, but if that doesn't work, there may be other bugs
<sb0> are misoc/artiq runtime all in sync with what is flashed in your board?
imrehg has quit [Quit: Leaving]
acathla has quit [Read error: Connection reset by peer]
acathla has joined #m-labs
acathla has quit [Changing host]
acathla has joined #m-labs
bentley` has quit [Ping timeout: 256 seconds]
acathla has quit [Quit: Coyote finally caught me]
acathla has joined #m-labs
bentley` has joined #m-labs
<whitequark> sb0: not right now, let me resync
<sb0> I have changed the rtio core CRSs a bit lately, that could be the problem.
<whitequark> hrm, does that mean I need to rebuild the bitstream again...
<whitequark> sb0: by the way, why don't you display anything on the console when an exception happens, but just hang?
<whitequark> new-py2llvm sort of does that now on kernel CPU (well, __artiq_raise in debug mode does) and it's like 500% more dev-friendly
<whitequark> oh, and DWARF debug info generation is now enabled in LLVM, so you can just pass -g and use objdump -S to map pc to line
<sb0> that's an oversight
<sb0> you mean uncaught exceptions, right?
<sb0> ?
<whitequark> right now __artiq_personality is not built with -NDEBUG, so all are logged
<whitequark> once it's turned off, none will be printed, and all will be sent back via RPC
<whitequark> except, perhaps, during idle experiment
<whitequark> (where do logs go during idle experiment?)
<sb0> all logs go to the serial console
<whitequark> but only with Ethernet.
<sb0> with the serial version, they are stored in a buffer that you can request
<whitequark> how do I do that, by the way? I don't recall anything in docs
<whitequark> (right now I just modify log to do puts)
<sb0> there is no CLI tool for that yet
<whitequark> oh
<whitequark> artiq_lastlog?
<whitequark> or what it was. artiq_logread
<sb0> merge it into artiq_coreconfig and rename to artiq_coretool?
<whitequark> mmm
<whitequark> as an API user, I would actually prefer two commands here
<whitequark> but I can do that.
<sb0> that would share the ddb management
<sb0> (args, opening, creating device, etc.)
<whitequark> ah right
<GitHub109> [misoc] whitequark pushed 1 new commit to master: http://git.io/vOn2W
<GitHub109> misoc/master 64f1368 whitequark: libunwind: build with -DNDEBUG.
<GitHub152> [artiq] whitequark force-pushed new-py2llvm from 122b3b0 to 62fdc75: http://git.io/vmI6O
<GitHub152> artiq/new-py2llvm 62fdc75 whitequark: Integrate libdyld and libunwind....
<whitequark> stekern: ^
<stekern> whitequark: those relocations are only used in eh_frame, right?
<whitequark> stekern: as far as I am aware.
<whitequark> they weren't ever emitted by LLVM until I patched it. not sure about gcc, but probably same.
<whitequark> I can't imagine any other reason a PC-relative data relocation would appear. all non-DWARF ones in regular data should be absolute since the frontend doesn't know to add the address of relocation when reading
<stekern> gcc should be emitting .eh_frame, but maybe those relocations aren't being used there
<whitequark> they should be used with -fPIC
<whitequark> well, it could probably also use absptr encoding
<whitequark> sb0: hm, brg_ddsinstall doesn't hang here either anymore
<whitequark> not sure what that was
<GitHub62> [artiq] whitequark pushed 1 new commit to new-py2llvm: http://git.io/vOnDA
<GitHub62> artiq/new-py2llvm 8d0222c whitequark: Rename artiq_coreconfig → artiq_coretool; add log subcommand.
<GitHub172> [artiq] whitequark pushed 1 new commit to master: http://git.io/vOnDx
<GitHub172> artiq/master ad7cbc4 whitequark: Rename artiq_coreconfig → artiq_coretool; add log subcommand.
travis-ci has joined #m-labs
<travis-ci> m-labs/artiq#370 (master - ad7cbc4 : whitequark): The build passed.
travis-ci has left #m-labs [#m-labs]
imrehg has joined #m-labs
_whitelogger has quit [Ping timeout: 240 seconds]
_whitelogger has joined #m-labs
<whitequark> sb0: ok, I have questions about the programming model of ARTIQ
<whitequark> do I understand this correctly...
<whitequark> you start from some subclass of Experiment. there is an implicitly created instance of Experiment on the device.
<whitequark> you use attr_whatever to give the class of that instance the corresponding attributes
<whitequark> every attribute, something like TTLOut, also pulls in its corresponding class and all its @kernel functions
<whitequark> this all happens recursively.
<whitequark> what would be really great is if I could discover the full extent of the classes whose attributes the kernel can call before even starting inference
<whitequark> interleaving inference and discovery is... it's possible, but it's kind of gnarly
imrehg has quit [Quit: Leaving]
<cr1901_modern> sb0: https://gist.github.com/cr1901/c20cbc5b1eb0d8d43578 Let me know if you need me to trim it more and I'll see what I can do.
chiggs has quit [*.net *.split]
mindrunner has quit [*.net *.split]
mindrunner has joined #m-labs
chiggs has joined #m-labs
early has quit [Ping timeout: 255 seconds]
early has joined #m-labs
mumptai has quit [Remote host closed the connection]