patches/gcc/4.4.3/110-trampolinewarn.patch
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Mon Mar 28 01:05:18 2011 +0200 (2011-03-28)
changeset 2362 0888065f8c4d
parent 1611 e2516bba8fe5
permissions -rw-r--r--
cc/gcc: cleanup the _or_later logic

So far, we've had a version always select appropriate _or_later option,
which in turn would select all previous _or_later options.

Because the dependencies on companion libs were cumulative, that was
working OK. But the upcoming 4.6 will no longer depend on libelf, so
we can't keep the cumulative scheme we've been using so far.

Have each release family select the corresponding dependencies, instead
of relying on selecting previous _or_later.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.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
     4 @@ -5768,6 +5768,9 @@
     5    trampolines_created = 1;
     6    INITIALIZE_TRAMPOLINE (r_tramp, r_func, r_chain);
     7  
     8 +  if (warn_trampolines)
     9 +    warning (OPT_Wtrampolines, "generating trampoline in object (requires executable stack)");
    10 +
    11    return const0_rtx;
    12  }
    13  
    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
    17 @@ -197,6 +197,10 @@
    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
    20  
    21 +Wtrampolines
    22 +Common Var(warn_trampolines) Init(1)
    23 +Warn whenever a trampoline is generated
    24 +
    25  Wuninitialized
    26  Common Var(warn_uninitialized) Warning
    27  Warn about uninitialized automatic variables