Skip to content
Snippets Groups Projects
  1. Mar 12, 2024
  2. Mar 01, 2024
  3. Sep 05, 2023
  4. Aug 31, 2023
  5. May 09, 2023
  6. May 02, 2023
  7. Apr 21, 2023
  8. Feb 21, 2023
  9. Feb 16, 2023
  10. Jan 06, 2023
  11. Jan 04, 2023
  12. Oct 04, 2022
  13. Sep 29, 2022
  14. Sep 09, 2022
  15. Aug 30, 2022
  16. Apr 22, 2022
  17. Apr 14, 2022
  18. Mar 21, 2022
    • Virgile Prevosto's avatar
      [kernel] Better casts introduction · b387e3bd
      Virgile Prevosto authored
      - always remove FC's internal attribute everywhere before deciding whether
        a cast is needed.
      - ACSL and C decisions to cast are similar
      - only unroll type for checking equality. If a cast is needed, keep
        typedef (if any) as target
      b387e3bd
  19. Mar 11, 2022
  20. Mar 10, 2022
  21. Feb 15, 2022
  22. Feb 08, 2022
  23. Jan 26, 2022
  24. Jan 20, 2022
  25. Jan 14, 2022
  26. Jan 06, 2022
  27. Dec 10, 2021
  28. Nov 18, 2021
    • Andre Maroneze's avatar
      [Libc] avoid spurious uninitialized warnings from the compiler · a3eb75e3
      Andre Maroneze authored
      Clang 13 emits warnings related to uninitialized variables:
      
      variable 'r' is used uninitialized whenever 'if'
      condition is false [-Wsometimes-uninitialized]
      
      This is due to the fact that the assert(0) macro, when using Frama-C's libc,
      is expanded to __FC_assert. Since it is not known by the compiler, it cannot
      consider it as "noreturn" when the condition is zero. Note that adding
      '__attribute__ ((__noreturn__))' will not work: Frama-C will assume it
      never returns, even when the condition is true.
      Initializing the 'r' variables with a default value will not change the
      actual behavior, and will avoid the warnings.
      a3eb75e3
  29. Nov 02, 2021
  30. Oct 19, 2021
Loading