On Thu, Jul 14, 2016 at 10:09 PM, Bram Moolenaar <[email protected]> wrote:
>
> Patch 7.4.2036
> Problem: Looking up a buffer by number is slow if there are many.
> Solution: Use a hashtab.
> Files: src/structs.h, src/buffer.c
This introduces several messages in the Tiny build for buffer.c, which
fails as follows (Huge build compiles and links normally):
gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
-U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/buffer.o
buffer.c
In file included from vim.h:1818:0,
from buffer.c:28:
buffer.c: In function ‘buf_hashtab_remove’:
structs.h:1099:70: error: ‘hash_removed’ undeclared (first use in this function)
#define HASHITEM_EMPTY(hi) ((hi)->hi_key == NULL || (hi)->hi_key ==
&hash_removed)
^
buffer.c:370:10: note: in expansion of macro ‘HASHITEM_EMPTY’
if (!HASHITEM_EMPTY(hi))
^
structs.h:1099:70: note: each undeclared identifier is reported only
once for each function it appears in
#define HASHITEM_EMPTY(hi) ((hi)->hi_key == NULL || (hi)->hi_key ==
&hash_removed)
^
buffer.c:370:10: note: in expansion of macro ‘HASHITEM_EMPTY’
if (!HASHITEM_EMPTY(hi))
^
buffer.c: In function ‘buflist_findnr’:
structs.h:1099:70: error: ‘hash_removed’ undeclared (first use in this function)
#define HASHITEM_EMPTY(hi) ((hi)->hi_key == NULL || (hi)->hi_key ==
&hash_removed)
^
buffer.c:2624:10: note: in expansion of macro ‘HASHITEM_EMPTY’
if (!HASHITEM_EMPTY(hi))
^
buffer.c: At top level:
buffer.c:366:1: warning: ‘buf_hashtab_remove’ defined but not used
[-Wunused-function]
buf_hashtab_remove(buf_T *buf)
^
Makefile:2770: recipe for target 'objects/buffer.o' failed
make: *** [objects/buffer.o] Error 1
exit status 2
Best regards,
Tony.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
