scripts/addToolsVersion: properly handle .in vs. .in.2
While most components have their version in the .in file, some
have it in the .in.2 (eg. elf2flt).
Currently, to handle this case, we indiscriminately munge both files,
but this is wrong: in the elf2flt case, if we add a binutils version,
we do not want it to be added to elf2flt, and conversely.
So, for each tool, we need to explicitly know what file to munge.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
1 Signed-off-by: dank@kegel.com
3 Raising the size of the hash table is a noticable win when linking
4 at least one large app.
7 http://sources.redhat.com/ml/binutils/2004-06/msg00165.html
8 to do this dynamically. No idea why that didn't make it in.
9 So this tiny change to raise the default size is just
13 --- binutils-2.17/bfd/hash.c.old 2006-03-02 23:01:39.000000000 -0800
14 +++ binutils-2.17/bfd/hash.c 2006-03-02 23:01:58.000000000 -0800
18 /* The default number of entries to use when creating a hash table. */
19 -#define DEFAULT_SIZE 4051
20 +#define DEFAULT_SIZE 32749
21 static size_t bfd_default_hash_table_size = DEFAULT_SIZE;
23 /* Create a new hash table, given a number of entries. */