DocScrutinizer05 changed the topic of #qi-hardware to: Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
rz2k has joined #qi-hardware
pcercuei has quit [Quit: dodo]
Textmode has joined #qi-hardware
porchao has quit [Quit: Leaving...]
jekhor has joined #qi-hardware
rz2k has quit [Read error: Connection reset by peer]
jekhor has quit [Ping timeout: 240 seconds]
xiangfu has joined #qi-hardware
<eintopf> larsc: contiki is a mess
<wpwrak> larsc: you should contract eintopf so he can give an inspirational speech after pcercuei's pitch ;-)
<larsc> hehe :)
xiangfu has quit [Ping timeout: 260 seconds]
<eintopf> wpwrak: ... but works better than linux implementation
<eintopf> and maybe the best supported 6lowpan stack
porchao has joined #qi-hardware
Textmode has quit [Quit: "It was one dev, naked in a room with a carton of cigarettes, a thermos full of coffee and bourbon, and all his summoned angels."]
xiangfu has joined #qi-hardware
rz2k has joined #qi-hardware
xiangfu has quit [Ping timeout: 264 seconds]
pcercuei has joined #qi-hardware
<eintopf> grml
<eintopf> I also get the warning of unused jump variable at kconfig since 4.9.0 which is also a compiler bug
<larsc> time to switch to clang?
<whitequark> clang still fails on 10% of debian
<whitequark> that will go down considerably with 3.5, but... still a long time until that's realistc
<larsc> fails as in doesn't build or generates broken binaries?
<pcercuei> can it compile the kernel yet?
<larsc> most of it I think
<mth> whitequark: is that an x86-64 specific issue?
<whitequark> redzone is x86_64-specific
<whitequark> although iirc ppc has a similar thing
<whitequark> (but probably no similar gcc bug)
<mth> ok, we're using gcc 4.9.1 on mipsel and the test case didn't trigger a bug, but I wasn't sure if that means we're safe or the test case is just too specific
<whitequark> you wouldn't also easily trigger it on x86_64
<whitequark> unless you perform a lot of testing
<whitequark> it's a sort of race condition
<whitequark> oh, wait, you said test case
<whitequark> nevermind what I said
rz2k has quit []
_whitelogger has quit [K-Lined]
_whitelogger has joined #qi-hardware
whitequark has joined #qi-hardware
jekhor has joined #qi-hardware
jekhor has quit [Ping timeout: 255 seconds]
zcrc has joined #qi-hardware
zcrc has quit [Read error: Connection reset by peer]
pcercuei_ has joined #qi-hardware
dos1 has quit [Ping timeout: 240 seconds]
dos1 has joined #qi-hardware
pcercuei_ is now known as zcrc