My darktable is rebuilding all the cache, this is annoying when having
more than 40k images. I've checked in the commit what could have
invalidated the cache, maybe:
commit 3fc5cd4c6c2536689c4d9566b618f5ace49be520
Author: Roman Lebedev <lebedev...@gmail.com>
Date: Mon Sep 8 02:34:21 2014 +0400
struct dt_mipmap_buffer_dsc: use __attribute__((packed,aligned(16)))
for padding
Type size_ะต may have different size on 32-bit machines, so let's try
to make compiler do the padding.
diff --git a/src/common/mipmap_cache.c b/src/common/mipmap_cache.c
index c0007fb..493db53 100644
--- a/src/common/mipmap_cache.c
+++ b/src/common/mipmap_cache.c
@@ -54,12 +54,9 @@ struct dt_mipmap_buffer_dsc
uint32_t width;
uint32_t height;
size_t size;
- uint32_t padding1; //
- uint32_t padding2; // FIXME: any better way ?
- uint32_t padding3; //
uint32_t flags;
/* NB: sizeof must be a multiple of 4*sizeof(float) */
-} __attribute__((packed));
+} __attribute__((packed,aligned(16)));
// last resort mem alloc for dead images. sizeof(dt_mipmap_buffer_dsc) +
dead image pixels (8x8)
// __m128 type for sse alignment.
Is that it?
--
Pascal Obry / Magny Les Hameaux (78)
The best way to travel is by means of imagination
http://v2p.fr.eu.org
http://www.obry.net
gpg --keyserver keys.gnupg.net --recv-key F949BD3B
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
