Skip to content

S
Simple VME FMC Carrier SVEC
Switch branch/tag
  1. 22 Mar, 2021 2 commits
  3. 16 Mar, 2021 1 commit
  5. 08 Feb, 2021 1 commit
  7. 05 Jan, 2021 2 commits
  9. 24 Nov, 2020 2 commits
  11. 03 Nov, 2020 1 commit
  13. 27 Oct, 2020 2 commits
  15. 26 Oct, 2020 1 commit
  17. 22 Oct, 2020 2 commits
  19. 15 Sep, 2020 2 commits
  21. 11 Sep, 2020 5 commits
  23. 03 Jun, 2020 3 commits
  25. 14 Apr, 2020 5 commits
  27. 10 Mar, 2020 1 commit
  29. 03 Mar, 2020 1 commit
    • Dimitris Lampridis's avatar
      driver: respect stack frame limit · 181ad487
      Dimitris Lampridis authored 
      svec_fpga_app_init() declares too many local buffers that are allocated on the stack.

On some versions of GCC this is detected and reported, causing a warning that is promoted to an
error. Example:

svec-core-fpga.c:710:1: error: the frame size of 1968 bytes is larger than 1024 bytes
[-Werror=frame-larger-than=]

Since apparently it is not a very good idea to increase the stack frame size limit [1], the solution
implemented here is to switch to dynimically allocating the biggest buffer (struct resource res[]).

[1]: https://gcc.gnu.org/onlinedocs/gccint/Stack-Checking.html#Stack-Checking
"The maximum size of a stack frame, in bytes. GCC will generate probe instructions in non-leaf
functions to ensure at least this many bytes of stack are available. If a stack frame is larger than
this size, stack checking will not be reliable and GCC will issue a warning. The default is chosen
so that GCC only generates one instruction on most systems. You should normally not change the
default value of this macro."
Signed-off-by: Dimitris Lampridis's avatarDimitris Lampridis <dimitris.lampridis@cern.ch>
      181ad487
  31. 17 Feb, 2020 3 commits
  33. 12 Feb, 2020 1 commit
  35. 15 Jan, 2020 1 commit
  37. 16 Dec, 2019 4 commits