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 Original patch from gentoo: gentoo/src/patchsets/gcc/4.3.1/gentoo/64_all_gcc43-pr34571.patch
2 http://gcc.gnu.org/PR34571
4 2007-12-26 Rask Ingemann Lambertsen <rask@sygehus.dk>
7 * config/alpha/alpha.c (alpha_cannot_force_const_mem): Use
9 * varasm.c (output_constant_pool_1): Fix typo.
11 diff -durN gcc-4.3.1.orig/gcc/config/alpha/alpha.c gcc-4.3.1/gcc/config/alpha/alpha.c
12 --- gcc-4.3.1.orig/gcc/config/alpha/alpha.c 2008-02-07 18:45:24.000000000 +0100
13 +++ gcc-4.3.1/gcc/config/alpha/alpha.c 2008-06-10 14:58:24.000000000 +0200
16 alpha_cannot_force_const_mem (rtx x)
18 - enum rtx_code code = GET_CODE (x);
19 - return code == SYMBOL_REF || code == LABEL_REF || code == CONST;
20 + return symbolic_operand (x, GET_MODE (x));
23 /* We do not allow indirect calls to be optimized into sibling calls, nor
24 diff -durN gcc-4.3.1.orig/gcc/varasm.c gcc-4.3.1/gcc/varasm.c
25 --- gcc-4.3.1.orig/gcc/varasm.c 2007-12-05 22:55:10.000000000 +0100
26 +++ gcc-4.3.1/gcc/varasm.c 2008-06-10 14:58:24.000000000 +0200
32 + tmp = XEXP (tmp, 0);
33 gcc_assert (!INSN_DELETED_P (tmp));
34 gcc_assert (!NOTE_P (tmp)
35 || NOTE_KIND (tmp) != NOTE_INSN_DELETED);