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
<GitHub12> [smoltcp] crawford commented on issue #97: Ah, that makes sense. Thank you! https://github.com/m-labs/smoltcp/issues/97#issuecomment-353809136
<GitHub44> [llvm-or1k] whitequark force-pushed artiq-5.0 from ec27435 to 7f08a12: https://github.com/m-labs/llvm-or1k/commits/artiq-5.0
<GitHub89> [llvm-or1k] whitequark force-pushed master from ec27435 to 7f08a12: https://github.com/m-labs/llvm-or1k/commits/master
<GitHub144> [artiq] whitequark commented on issue #655: Per correspondence with LLVM developers, the patch is broken by design and cannot be fixed (and likely can lead to miscompilations already). We'll have to find some other way of improving the performance of the loops it was used to speed up. https://github.com/m-labs/artiq/issues/655#issuecomment-353810249
<GitHub1> [artiq] whitequark closed issue #655: Unbreak the !unconditionally_dereferenceable LLVM patch https://github.com/m-labs/artiq/issues/655
<whitequark> sb0: who are the right OR1K people to talk about if I need to extend the ABI?
<whitequark> two 32-bit return registers are not enough
<GitHub141> [llvm-or1k] whitequark pushed 1 new commit to artiq-5.0: https://github.com/m-labs/llvm-or1k/commit/1c49b6f981a6bb9f737c9559b73b2f768a1d558d
<GitHub141> llvm-or1k/artiq-5.0 1c49b6f whitequark: [OR1K] Add two more return registers, R13 and R15....
<sb0> whitequark, maybe stekern ?
<whitequark> stekern: ^ I've used R13 and R15 for this. it shouldn't affect anything other than LLVM intrinsics, I think, JFYI
<cr1901_modern> How can you fast forward thousands of commits without the directory structure or something in the build system itself breaking?
<whitequark> it's LLVM
<whitequark> they don't change the build system all that much, and they do a lot of very small incremental commits
<whitequark> github doesn't properly show commit #'s by the way, that was somewhere around 5000 commits I think?
<cr1901_modern> Well, directory structure was changed between 3.minor-version-cpu0-version uses and 3.9 (which is the version I'm slowly hacking on)
<cr1901_modern> (that second "version" should be tutorial)
<whitequark> 3.0 to 3.9 spans like a decade
<whitequark> and a migration from autocrap to cmake
<cr1901_modern> Okay I'll take your word for it. I'm prob filled with FUD when I inevitably try to rebase on top of 4.x
<cr1901_modern> or 5.x- whatever the new version scheme is
<whitequark> 4.x converted a few pointers to references and added an argument here and there
<whitequark> 5.x converted a few more pointers to references
<whitequark> that's it
<whitequark> oh and if cpu0 has relocations then relocation def files moved too
<cr1901_modern> yes those were the files I was thinking of in particular
<whitequark> it's exactly one file
<whitequark> it's really not hard to fix, this took me less than ten minutes per version
<whitequark> plus a hour of compiling all the crap
<whitequark> also, don't rebase, merge
<cr1901_modern> i.e. checkout 4.x/5.x branch and just merge from the tip of my altered 3.9 branch?
<whitequark> fetch upstream/release_{40,50}
<whitequark> erm
<whitequark> `git fetch upstream && git merge upstream/release_40`
<whitequark> then for 50
<cr1901_modern> Oh duh (I'm totally not on release_39 anyway. My branch's ancestor is release_39 of course)
<GitHub51> [smoltcp] LuoZijun commented on issue #82: @liranringel ... https://github.com/m-labs/smoltcp/issues/82#issuecomment-353822042
<stekern> whitequark: you should speak to Stafford Horne (shorne on irc), he's the one that's been most active touching the arch definitions lately
_rht has joined #m-labs
_whitelogger has joined #m-labs
_rht has quit [Quit: Connection closed for inactivity]
<whitequark> stekern: which IRC?
<whitequark> IRC channel*
<GitHub97> [rust] whitequark created artiq-1.22.1 (+2744 new commits): https://github.com/m-labs/rust/compare/230668765d5a^...32989f61a591
<GitHub97> rust/artiq-1.22.1 39b8aaf Felix S. Klock II: Slew of feature gating tests for issue #43106.
<GitHub97> rust/artiq-1.22.1 ba53f95 Ralf Jung: E0122: clarify wording
<GitHub97> rust/artiq-1.22.1 2306687 Johannes Löthberg: Add support for full RELRO...
<GitHub121> [smoltcp] whitequark opened issue #104: Implement TCP Fast Retransmit https://github.com/m-labs/smoltcp/issues/104
<GitHub172> [smoltcp] whitequark opened issue #105: Implement support for jumbo frames https://github.com/m-labs/smoltcp/issues/105
<GitHub0> [smoltcp] whitequark opened issue #106: Implement TCP window scaling https://github.com/m-labs/smoltcp/issues/106
<whitequark> of *course* the upgrade to LLVM 5.0 broke something in rust's liballoc...
<whitequark> this is why we should upgrade every time a new version comes out and not in these massive chunks once a year
<sb0> why are we upgrading right now?
<whitequark> because smoltcp tickled some rustc bug
<whitequark> in 1.20.0
<whitequark> well, I'm working on backtraces now, so it's all good
<whitequark> sb0: $(compile) -D_LIBUNWIND_BARE_METAL
<whitequark> this doesn't work
<whitequark> what should I use instead?
<whitequark> (in misoc)
<sb0> whitequark, what are you trying to do, pass an additional flag to the compiler?
<whitequark> yes
<whitequark> but only in some rules
<sb0> maybe copy what compile expands to?
<sb0> $(CC) -c $(CFLAGS) -D_LIBUNWIND_BARE_METAL $(1) $< -o $@
<whitequark> that's ugly...
<whitequark> why even bother with the short form in the first place
<sb0> makefiles are ugly
<sb0> why does $(compile) -D_LIBUNWIND_BARE_METAL break anyway?
<whitequark> not a clue
<whitequark> oh hm, it does pass the argument
<whitequark> nevermind
X-Scale has joined #m-labs
<GitHub35> [misoc] whitequark pushed 2 new commits to master: https://github.com/m-labs/misoc/compare/123a5d593571...876eeb173430
<GitHub35> misoc/master 06fb383 whitequark: software: extract libprintf from libbase....
<GitHub35> misoc/master 876eeb1 whitequark: software: clean up Makefiles.
<GitHub81> [misoc] whitequark pushed 1 new commit to master: https://github.com/m-labs/misoc/commit/e09d84d791de32ab92b2c33a42b690139a26b00e
<GitHub81> misoc/master e09d84d whitequark: software: fix typo.
<bb-m-labs> build #310 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/310
<bb-m-labs> build #311 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/311
<GitHub139> [misoc] whitequark pushed 1 new commit to master: https://github.com/m-labs/misoc/commit/727187d43aeb542101aed3f46ef8650c119a5bea
<GitHub139> misoc/master 727187d whitequark: libprintf: inline strnlen to avoid a libbase dependency....
<bb-m-labs> build #312 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/312
<whitequark> "rotting FPGA designs"
<whitequark> sb0: your printf implementation only worked because it invoked unsigned underflow in strnlen.
<whitequark> C was a mistake.
<sb0> whitequark, where did that printf come from again? it was either newlib or linux kernel
<whitequark> linux
<whitequark> but I don't recall linux's printf being *this* shitty
<whitequark> maybe if you took some very old version of it...
<GitHub189> [misoc] whitequark pushed 1 new commit to master: https://github.com/m-labs/misoc/commit/88ffbb6e4b638f08617d6790da5aeff22a7d4d20
<GitHub189> misoc/master 88ffbb6 whitequark: libprintf: unbreak %s....
<bb-m-labs> build #313 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/313
<whitequark> sb0: backtraces work.
<whitequark> and I'll even upstream them in libunwind...
<GitHub44> [misoc] whitequark pushed 1 new commit to master: https://github.com/m-labs/misoc/commit/a3bc1b8d1bff942af3394fc3ede0c96ad9282ea2
<GitHub44> misoc/master a3bc1b8 whitequark: libunwind: update, split into libunwind-elf.a and libunwind-bare.a.
<bb-m-labs> build #314 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/314
<rqou> whitequark: in case you want a "not too bad" standalone printf: https://github.com/rqou/standalone-printf-scanf/blob/master/standalone_printf.c
<rqou> this one is ripped from musl
<whitequark> eh, I already fixed it
<GitHub39> [misoc] whitequark pushed 1 new commit to master: https://github.com/m-labs/misoc/commit/d95f4edb04987fc4de0cffa46608f41d06b85ead
<GitHub39> misoc/master d95f4ed whitequark: libunwind: build GCC extension APIs.
<bb-m-labs> build #315 of misoc is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/misoc/builds/315
<GitHub120> [artiq] whitequark pushed 3 new commits to master: https://github.com/m-labs/artiq/compare/70b7f28ad35f...3eec15c01d0b
<GitHub120> artiq/master fa4dc1b whitequark: doc: developing: show how to make clang source builds faster.
<GitHub120> artiq/master 1570a48 whitequark: artiq_devtool: don't require lock for reset....
<GitHub120> artiq/master 3eec15c whitequark: firmware: fix compatibility with newer rustc. NFC.
f4bug has quit [Quit: Leaving.]
<bb-m-labs> build #983 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/983
<bb-m-labs> build #645 of artiq-win64-test is complete: Warnings [warnings python_coverage] Build details are at http://buildbot.m-labs.hk/builders/artiq-win64-test/builds/645 blamelist: whitequark <whitequark@whitequark.org>
<bb-m-labs> build #1857 of artiq is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1857
<GitHub59> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/230f2e5e18726e8c4b3ed72a78d0fe4aa48fd701
<GitHub59> artiq/master 230f2e5 whitequark: runtime: print (address-only) backtraces on core device panics.
<bb-m-labs> build #984 of artiq-board is complete: Failure [failed conda_build] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/984 blamelist: whitequark <whitequark@whitequark.org>
<bb-m-labs> build #1858 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1858 blamelist: whitequark <whitequark@whitequark.org>
<GitHub140> [artiq] whitequark pushed 1 new commit to master: https://github.com/m-labs/artiq/commit/061fb3dcd52df714b5f7c7ea51350ba776d2a44b
<GitHub140> artiq/master 061fb3d whitequark: runtime: remove accidentally committed parts of a Makefile.
<bb-m-labs> build #985 of artiq-board is complete: Success [build successful] Build details are at http://buildbot.m-labs.hk/builders/artiq-board/builds/985
<bb-m-labs> build #1859 of artiq is complete: Failure [failed] Build details are at http://buildbot.m-labs.hk/builders/artiq/builds/1859 blamelist: whitequark <whitequark@whitequark.org>
X-Scale has quit [Quit: HydraIRC -> http://www.hydrairc.com <- In tests, 0x09 out of 0x0A l33t h4x0rz prefer it :)]
<whitequark> *stare*
<whitequark> panic at src/libcore/slice/mod.rs:735: index 1869492536 out of range for slice of length 65536
<whitequark> this makes no sense
<whitequark> of course, the backtraces aren't symbolized yet, so I don't know where this actually happens...
X-Scale has joined #m-labs