2014-07-26 00:10 rz2k has joined #qi-hardware 2014-07-26 01:46 pcercuei has quit [Quit: dodo] 2014-07-26 03:35 Textmode has joined #qi-hardware 2014-07-26 03:35 porchao has quit [Quit: Leaving...] 2014-07-26 04:15 jekhor has joined #qi-hardware 2014-07-26 04:31 rz2k has quit [Read error: Connection reset by peer] 2014-07-26 04:47 jekhor has quit [Ping timeout: 240 seconds] 2014-07-26 05:32 xiangfu has joined #qi-hardware 2014-07-26 06:14 larsc: contiki is a mess 2014-07-26 06:27 larsc: you should contract eintopf so he can give an inspirational speech after pcercuei's pitch ;-) 2014-07-26 07:07 hehe :) 2014-07-26 07:08 xiangfu has quit [Ping timeout: 260 seconds] 2014-07-26 07:28 wpwrak: ... but works better than linux implementation 2014-07-26 07:29 and maybe the best supported 6lowpan stack 2014-07-26 07:35 porchao has joined #qi-hardware 2014-07-26 07:55 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."] 2014-07-26 09:40 xiangfu has joined #qi-hardware 2014-07-26 09:44 rz2k has joined #qi-hardware 2014-07-26 10:38 xiangfu has quit [Ping timeout: 264 seconds] 2014-07-26 11:44 pcercuei has joined #qi-hardware 2014-07-26 12:16 https://lkml.org/lkml/2014/7/24/584 2014-07-26 12:32 grml 2014-07-26 12:32 I also get the warning of unused jump variable at kconfig since 4.9.0 which is also a compiler bug 2014-07-26 12:44 time to switch to clang? 2014-07-26 12:45 clang still fails on 10% of debian 2014-07-26 12:45 that will go down considerably with 3.5, but... still a long time until that's realistc 2014-07-26 12:48 fails as in doesn't build or generates broken binaries? 2014-07-26 12:50 http://clang.debian.net 2014-07-26 12:51 can it compile the kernel yet? 2014-07-26 12:52 most of it I think 2014-07-26 12:52 http://llvm.linuxfoundation.org/ 2014-07-26 13:50 whitequark: is that an x86-64 specific issue? 2014-07-26 13:50 redzone is x86_64-specific 2014-07-26 13:50 although iirc ppc has a similar thing 2014-07-26 13:50 (but probably no similar gcc bug) 2014-07-26 13:51 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 2014-07-26 13:51 you wouldn't also easily trigger it on x86_64 2014-07-26 13:51 unless you perform a lot of testing 2014-07-26 13:51 it's a sort of race condition 2014-07-26 13:52 oh, wait, you said test case 2014-07-26 13:52 nevermind what I said 2014-07-26 13:52 fair.i from the end of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61904 2014-07-26 14:54 rz2k has quit [] 2014-07-26 20:23 _whitelogger has quit [K-Lined] 2014-07-26 20:23 _whitelogger has joined #qi-hardware 2014-07-26 20:23 whitequark has joined #qi-hardware 2014-07-26 21:01 jekhor has joined #qi-hardware 2014-07-26 21:56 jekhor has quit [Ping timeout: 255 seconds] 2014-07-26 22:29 zcrc has joined #qi-hardware 2014-07-26 23:12 zcrc has quit [Read error: Connection reset by peer] 2014-07-26 23:12 pcercuei_ has joined #qi-hardware 2014-07-26 23:20 dos1 has quit [Ping timeout: 240 seconds] 2014-07-26 23:21 dos1 has joined #qi-hardware 2014-07-26 23:21 pcercuei_ is now known as zcrc