- 27 Jul, 2018 1 commit
-
-
Rusty Russell authored
I had a bug caused by using tal_len instead of tal_count: let's make it explicit. @jb55 commented "ha. I always forget which one does which... Ack" Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 04 Jul, 2018 1 commit
-
-
Rusty Russell authored
ccan/cppmagic FTW! The only issue is that we can't tell if there's padding or they've missed a member, so we add a padding bytes count, so they'll get an error if it (for example) the structure adds a new member later. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 18 Jun, 2018 1 commit
-
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 12 Jun, 2018 10 commits
-
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Groundwork for adding tests dynamically. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Works well with --autotools-style. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
This is the only non-text field. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Eric Wong authored
I don't see likely/unlikely being used by ccan/timer or any of its dependencies right now. Running `tools/ccanlint/ccanlint ccan/timer' reveals no regressions Signed-off-by: Eric Wong <normalperson@yhbt.net> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
-
- 10 May, 2018 1 commit
-
-
Rusty Russell authored
It defines __BYTE_ORDER to __BYTE_ORDER__; gcc complains when we define it to something else. Let it be already defined, but check that the value is what we expect. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 09 May, 2018 2 commits
-
-
Rusty Russell authored
php5 was finally removed from ozlabs.org, but php7.2 seems to work fine. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 06 Apr, 2018 3 commits
-
-
Kamil authored
gcc6 introduceed a new warning switched with -Wmisleading-identation. This caused to generate a compilation warning for if statement misleadingly indented, which caused HAVE_ASPRINTF to be defined as 0. Adding newline after an if statement fixes the problem.
-
Rusty Russell authored
Exracted (and slightly modified) from a MacOS PR for lightning. Based-on-patch-by: https://github.com/conanocSigned-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
(Taken from PR for lightning) Patch-from: https://github.com/conanocSigned-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 05 Apr, 2018 2 commits
-
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 26 Mar, 2018 7 commits
-
-
Rusty Russell authored
It's significantly faster because it assumes no deletion: 10000000,critbit iteration (nsec),316 10000000,critbit callback iteration (nsec),90 ... 10000000,critbit consecutive iteration (nsec),308 10000000,critbit consecutive callback iteration (nsec),78 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
We can't do the full range, but we can for a handful of bits (8). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Because intmap_after_() would simply examine the critbits to walk the tree, it wouldn't realize that it might be in the completely wrong tree. In this case: Bit 4: 0 1 / \ / \ 100000011 100001011 When we ask for intmap_after_(011111111) we would check the critbit, it's a 1, so we end up on the right leaf instead of the left. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
A critbit tree is a binary tree which keeps branches for each bit which differs in the leaves. It's a simple data structure, but not entirely simple to implement the primitives people expect, as this bus shows. The bug: I added an open iterator, and intmap_after_ for a random value would sometimes return the wrong node. Cause: we don't know what the prefix is as we iterate, so by only testing the critbits in the tree, we can end up in the wrong place. This is only a problem if the value isn't in the (sub)tree, but this can easily happen even with contiguous trees should deletion occur. You can see an example in the next patch, which adds a test. After finding a bug in my intmap_after() routine, I went searching for other implementations to see how they handled it. Most didn't provide an open-ended iterator like this, relying on callback iterators which don't allow deletion. Gah! The exception was https://github.com/blynn/blt/blob/master/blt.c#L179 which implements blt_ceil() which does this (if you add one to the key, at least). However, it does it by effectively finding a node, using that to derive the prefix, then walking down the tree again. That's pretty suboptimal. There are basically two choices if you want an efficient after() operation: to reimplement this approach with some optimizations (ie. keep branches as we descend, and when we get to the bottom and know the prefix, we know which branch to go down), or keep the bits which got to each node. The latter is more optimal, but less generally useful: for bit strings, for example, we could keep the bits in common on each node, rather than storing the entire string at the bottom. But in practice you'd be doing allocations to re-create the index if the caller wanted it. However, in this implementation our keys are 64 bits only, and we already use a u8 for the bit number: using a 64-bit value there consumes no more space (thanks to alignment). We can store the critbit by using the prefix capped by a bit: 0b10000...0000 means no prefix and highest bit is the critbit, and 0bxxxxx1000...000 means the prefix is xxxxxx and the critbit is the 6th highest bit. The penalty is that iteration 70% slower. It's still pretty fast though. Before: $ for i in `seq 5`; do ./speed 10000000; done | stats 10000000,random generation (nsec),3-4(3.2+/-0.4) 10000000,critbit insert (nsec),1530-1751(1633.2+/-80) 10000000,critbit successful lookup (nsec),1723-1993(1806.8+/-97) 10000000,critbit failed lookup (nsec),1763-2104(1933.6+/-1.3e+02) 10000000,critbit iteration (nsec),208-266(242.2+/-19) 10000000,critbit memory (bytes),48 10000000,critbit delete (nsec),1747-1861(1803.8+/-42) 10000000,critbit consecutive iteration (nsec),182-228(210+/-18) After: 10000000,random generation (nsec),3-4(3.2+/-0.4) 10000000,critbit insert (nsec),1533-1699(1628+/-65) 10000000,critbit successful lookup (nsec),1831-2104(1972.4+/-1e+02) 10000000,critbit failed lookup (nsec),1850-2152(2008.2+/-1.1e+02) 10000000,critbit iteration (nsec),304-324(312.8+/-7.5) 10000000,critbit memory (bytes),48 10000000,critbit delete (nsec),1617-1872(1752+/-99) 10000000,critbit consecutive iteration (nsec),303-318(311+/-5.4) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
I wrote these a while ago, dig them out. On my laptop, min-max(avg+/-stdev) of 5 runs: make && for i in `seq 5`; do ./speed 10000000; done | stats make: Nothing to be done for 'all'. 10000000,random generation (nsec),3-4(3.2+/-0.4) 10000000,critbit insert (nsec),1530-1751(1633.2+/-80) 10000000,critbit successful lookup (nsec),1723-1993(1806.8+/-97) 10000000,critbit failed lookup (nsec),1763-2104(1933.6+/-1.3e+02) 10000000,critbit iteration (nsec),208-266(242.2+/-19) 10000000,critbit memory (bytes),48 10000000,critbit delete (nsec),1747-1861(1803.8+/-42) 10000000,critbit consecutive iteration (nsec),182-228(210+/-18) 10000000,hash insert (nsec),396-424(412+/-9.6) 10000000,hash successful lookup (nsec),150-164(157.4+/-5.5) 10000000,hash failed lookup (nsec),163-178(170+/-5.5) 10000000,hash iteration (nsec),21-26(23.2+/-1.7) 10000000,hash memory (bytes),45 10000000,hash delete (nsec),179-194(183.6+/-5.3) Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 16 Mar, 2018 1 commit
-
-
Jan Sarenik authored
Error I experienced on Alpine Linux without this patch: In file included from ccan/generator/generator.c:8:0: ./ccan/generator/generator.h:23:2: error: #error Generators require coroutines #error Generators require coroutines ^~~~~ make: *** [Makefile:32: ccan/generator/generator.o] Error 1
-
- 14 Mar, 2018 2 commits
-
-
Yubin Ruan authored
From 32f86c701ab0e0ad0ad6981314a9bff2dc5ebb74 Mon Sep 17 00:00:00 2001 From: Yubin Ruan <ablacktshirt@gmail.com> Date: Wed, 14 Mar 2018 11:14:54 +0800 Subject: [PATCH] fix misuse of typesafe_cb_cast() in example Signed-off-by: Yubin Ruan <ablacktshirt@gmail.com> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
-
Yubin Ruan authored
From 47c92fe951545e780ca31c598bbcbe5347059b27 Mon Sep 17 00:00:00 2001 From: Yubin Ruan <ablacktshirt@gmail.com> Date: Mon, 12 Mar 2018 11:22:35 +0800 Subject: [PATCH] fix misspelling in the example of container_of Signed-off-by: Yubin Ruan <ablacktshirt@gmail.com> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
-
- 01 Mar, 2018 1 commit
-
-
Rusty Russell authored
We already handle normal free traversal loops, just not ones caused by a direct tal_free() call, such a calling tal_free() on one's own parent. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 26 Feb, 2018 2 commits
-
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
Rusty Russell authored
This is for cross-configuring, where we might want to run `qemu-user-... gcc` or even more exotic things. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 16 Feb, 2018 1 commit
-
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 04 Feb, 2018 1 commit
-
-
Rusty Russell authored
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 21 Dec, 2017 1 commit
-
-
Rusty Russell authored
It seems most sensible to make it a noop, but it definitely shouldn't access out of bounds as it does. Reported-by: Russ Dill Fixes: #61 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 22 Nov, 2017 1 commit
-
-
Rusty Russell authored
Fixes: #63 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 25 Oct, 2017 1 commit
-
-
Rusty Russell authored
For lightning, we want to hand the socket off to another daemon, but we need to be on a packet boundary. This lets us check if we've part-read or part-written. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-
- 12 Oct, 2017 1 commit
-
-
Rusty Russell authored
If io_read is always called, we don't know that it will actually read, so it might not notice error. In that case, safest to fail immediately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
-