1. 29 Jul, 2021 1 commit
  2. 07 Jul, 2021 2 commits
  3. 22 Mar, 2021 2 commits
  4. 16 Mar, 2021 1 commit
  5. 08 Feb, 2021 1 commit
  6. 05 Jan, 2021 2 commits
  7. 24 Nov, 2020 2 commits
  8. 03 Nov, 2020 1 commit
  9. 27 Oct, 2020 2 commits
  10. 26 Oct, 2020 1 commit
  11. 22 Oct, 2020 2 commits
  12. 15 Sep, 2020 2 commits
  13. 11 Sep, 2020 5 commits
  14. 03 Jun, 2020 3 commits
  15. 14 Apr, 2020 5 commits
  16. 10 Mar, 2020 1 commit
  17. 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
  18. 17 Feb, 2020 3 commits
  19. 12 Feb, 2020 1 commit
  20. 15 Jan, 2020 1 commit
  21. 16 Dec, 2019 1 commit