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 diff -durN gcc-4.4.0.orig/gcc/builtins.c gcc-4.4.0/gcc/builtins.c
2 --- gcc-4.4.0.orig/gcc/builtins.c 2009-03-30 19:42:27.000000000 +0200
3 +++ gcc-4.4.0/gcc/builtins.c 2009-05-27 21:38:01.000000000 +0200
5 trampolines_created = 1;
6 INITIALIZE_TRAMPOLINE (r_tramp, r_func, r_chain);
8 + if (warn_trampolines)
9 + warning (OPT_Wtrampolines, "generating trampoline in object (requires executable stack)");
14 diff -durN gcc-4.4.0.orig/gcc/common.opt gcc-4.4.0/gcc/common.opt
15 --- gcc-4.4.0.orig/gcc/common.opt 2009-03-28 18:28:45.000000000 +0100
16 +++ gcc-4.4.0/gcc/common.opt 2009-05-27 21:38:01.000000000 +0200
18 Common Var(warn_type_limits) Init(-1) Warning
19 Warn if a comparison is always true or always false due to the limited range of the data type
22 +Common Var(warn_trampolines) Init(1)
23 +Warn whenever a trampoline is generated
26 Common Var(warn_uninitialized) Warning
27 Warn about uninitialized automatic variables