Renamed VERIFAST_PROOF define into VERIFAST.

verification/verifast/proof_setup/generated/pico_base/pico/config_autogen.h

@@ -6,7 +6,7 @@
 
 // based on PICO_CONFIG_HEADER_FILES:
 
-#ifdef VERIFAST_PROOF
+#ifdef VERIFAST
     /* Reason for rewrite: VeriFast cannot handle absolute include paths. */
     #include "freertos_sdk_config.h"
     #include "boards/pico.h"

verification/verifast/proof_setup/sys/cdefs.h

@@ -70,7 +70,7 @@
 #define _CDEFS_H_
 
 /* Verifast proof setup */
-#ifdef VERIFAST_PROOF
+#ifdef VERIFAST
     /*
      * The proof setup header is already included at the top of the proof target,
      * e.g., `tasks.c`. But it seems like the contained defines are not propagated

verification/verifast/proof_setup/verifast_proof_defs.h

@@ -7,7 +7,7 @@
 // /Users/reitobia/repos/forked/FreeRTOS-Kernel/verification/verifast/proof_setup_incremental/verifast_proof_defs.h
 
 
-#ifndef VERIFAST_PROOF_DEFS_H
+#ifndef VERIFAST_DEFS_H
     // The following defines are required by `FRTOS.h`
     // line 93
     #define configMAX_PRIORITIES 100
@@ -21,4 +21,4 @@
     #define __arm__
 
 
-#endif /* VERIFAST_PROOF_DEFS_H */
+#endif /* VERIFAST_DEFS_H */

verification/verifast/sdks/pico-sdk

@@ -1 +1 @@
-Subproject commit 0c8802074d519ed0354400d85113c98618277c8b
+Subproject commit 649256491cc60f331d39d2d06def7da8ede91790

verification/verifast/start-vfide.sh

@@ -29,7 +29,7 @@ PICO_SDK_DIR="sdks/pico-sdk"
 # `$GENERATED_HEADERS_DIR/pico_base`
 
 "$VFIDE" -I "$HEADER_DIR" \
--I $PROOF_SETUP_DIR -D VERIFAST_PROOF "$TASKS_C" \
+-I $PROOF_SETUP_DIR -D VERIFAST "$TASKS_C" \
 -I $FREERTOS_SMP_DEMO_DIR/FreeRTOS/Source/portable/ThirdParty/GCC/RP2040/include \
 -I $PICO_SDK_DIR/src/common/pico_base/include \
 -I $FREERTOS_SMP_DEMO_DIR/FreeRTOS/Source/include  \