um: Increase stack frame size threshold for signal.c
authorAndy Shevchenko <andriy.shevchenko@linux.intel.com>
Wed, 9 Dec 2020 18:19:15 +0000 (20:19 +0200)
committerRichard Weinberger <richard@nod.at>
Sun, 13 Dec 2020 21:22:00 +0000 (22:22 +0100)
commit517f60206ee5d5f75c44bd9c8b1683d1d18a616a
tree3ca716b34deae010935418bfb61bad946a11cf42
parentf4ab7818ef7add1e10b33d8c3a4fe44858b7f6e9
um: Increase stack frame size threshold for signal.c

The signal.c can't use heap for bit data located on stack. However,
by default a compiler warns us about overstepping stack frame size
threshold:

arch/um/os-Linux/signal.c: In function ‘sig_handler_common’:
arch/um/os-Linux/signal.c:51:1: warning: the frame size of 2960 bytes is larger than 2048 bytes [-Wframe-larger-than=]
   51 | }
      | ^
arch/um/os-Linux/signal.c: In function ‘timer_real_alarm_handler’:
arch/um/os-Linux/signal.c:95:1: warning: the frame size of 2960 bytes is larger than 2048 bytes [-Wframe-larger-than=]
    95 | }
       | ^

Due to above increase stack frame size threshold explicitly for signal.c
to avoid unnecessary warning.

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Tested-by: David Gow <davidgow@google.com>
Signed-off-by: Richard Weinberger <richard@nod.at>
arch/um/os-Linux/Makefile