| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | util: Helper to create sets and hashes with pointer keys | Caio Marcelo de Oliveira Filho | 2019-01-14 | 1 | -0/+3 |
| | | | | | | | | These combinations are common enough and deserve a shortcut. Reviewed-by: Jason Ekstrand <[email protected]> Acked-by: Eric Engestrom <[email protected]> | ||||
| * | util: use C99 declaration in the for-loop set_foreach() macro | Eric Engestrom | 2018-10-25 | 1 | -3/+3 |
| | | | | | | Signed-off-by: Eric Engestrom <[email protected]> Reviewed-by: Timothy Arceri <[email protected]> | ||||
| * | util/set: helper to remove entry by key | Caio Marcelo de Oliveira Filho | 2018-07-12 | 1 | -0/+2 |
| | | | | | | | v2: Add unit test. (Eric Anholt) Reviewed-by: Eric Anholt <[email protected]> | ||||
| * | util/set: add a clone function | Caio Marcelo de Oliveira Filho | 2018-07-12 | 1 | -0/+3 |
| | | | | | | | v2: Add unit test. (Eric Anholt) Reviewed-by: Eric Anholt <[email protected]> | ||||
| * | util/set: add a set_clear function | Scott D Phillips | 2018-05-04 | 1 | -0/+3 |
| | | | | | | | | Clear a set back to the state of having zero entries. Reviewed-by: Kenneth Graunke <[email protected]> Reviewed-by: Jason Ekstrand <[email protected]> | ||||
| * | util/hash_set: Rework the API to know about hashing | Jason Ekstrand | 2015-01-15 | 1 | -3/+9 |
| | | | | | | | | | | | | | | | | | | | | | | | | | Previously, the set API required the user to do all of the hashing of keys as it passed them in. Since the hashing function is intrinsically tied to the comparison function, it makes sense for the hash set to know about it. Also, it makes for a somewhat clumsy API as the user is constantly calling hashing functions many of which have long names. This is especially bad when the standard call looks something like _mesa_set_add(ht, _mesa_pointer_hash(key), key); In the above case, there is no reason why the hash set shouldn't do the hashing for you. We leave the option for you to do your own hashing if it's more efficient, but it's no longer needed. Also, if you do do your own hashing, the hash set will assert that your hash matches what it expects out of the hashing function. This should make it harder to mess up your hashing. This is analygous to 94303a0750 where we did this for hash_table Signed-off-by: Jason Ekstrand <[email protected]> Reviewed-by: Matt Turner <[email protected]> Reviewed-by: Eric Anholt <[email protected]> | ||||
| * | util: Move main/set to util/hash_set | Jason Ekstrand | 2015-01-15 | 1 | -0/+94 |
| Reviewed-by: Matt Turner <[email protected]> Reviewed-by: Eric Anholt <[email protected]> | |||||
 |
index : mesa.git | |
| Unnamed repository; edit this file 'description' to name the repository. |
| summaryrefslogtreecommitdiffstats |