Add Smith.

.clang-tidy

@@ -13,6 +13,7 @@ misc-*,
 llvm-*,
 google-*,
 -modernize-use-trailing-return-type,
+-misc-confusable-identifiers,
 -readability-identifier-length,
 -cppcoreguidelines-owning-memory,
 -bugprone-easily-swappable-parameters,

backends/p4tools/common/p4ctool.h

@@ -38,7 +38,7 @@ class AbstractP4cTool {
         auto &toolOptions = Options::get();
         auto compileContext = toolOptions.process(args);
         if (!compileContext) {
-            return 1;
+            return EXIT_FAILURE;
         }
 
         // Set up the compilation context.

backends/p4tools/modules/smith/CMakeLists.txt

@@ -0,0 +1,84 @@
+# CMake file for P4Smith.
+
+include(common)
+
+project(smith)
+
+# Declare common P4Testgen variables.
+set(P4SMITH_DIR ${P4C_BINARY_DIR}/smith)
+set(P4SMITH_DRIVER "${CMAKE_CURRENT_BINARY_DIR}/p4smith")
+
+configure_file(
+  "${CMAKE_CURRENT_SOURCE_DIR}/version.h.cmake" "${CMAKE_CURRENT_BINARY_DIR}/version.h" @ONLY
+)
+# Source files for smith.
+set(SMITH_SOURCES
+  core/target.cpp
+  common/declarations.cpp
+  common/expressions.cpp
+  common/parser.cpp
+  common/scope.cpp
+  common/statements.cpp
+  common/table.cpp
+  util/util.cpp
+  util/wordlist.cpp
+  options.cpp
+  smith.cpp
+)
+
+set(SMITH_LIBS
+  PRIVATE p4tools-common
+)
+
+file(GLOB tools_targets RELATIVE ${CMAKE_CURRENT_SOURCE_DIR}/targets
+     ${CMAKE_CURRENT_SOURCE_DIR}/targets/*
+)
+
+foreach(ext ${tools_targets})
+  if(EXISTS ${CMAKE_CURRENT_SOURCE_DIR}/targets/${ext}/CMakeLists.txt)
+    # Generate an option that makes it possible to disable this extension.
+    string(MAKE_C_IDENTIFIER ${ext} EXT_AS_IDENTIFIER)
+    string(TOUPPER ${EXT_AS_IDENTIFIER} EXT_AS_OPTION_NAME)
+    string(CONCAT ENABLE_EXT_OPTION "ENABLE_TOOLS_TARGET_" ${EXT_AS_OPTION_NAME})
+    string(CONCAT EXT_HELP_TEXT "Build the " ${ext} " target")
+    option(${ENABLE_EXT_OPTION} ${EXT_HELP_TEXT} ON)
+    if(${ENABLE_EXT_OPTION})
+      message("-- Enabling target ${ext}")
+      add_subdirectory(${CMAKE_CURRENT_SOURCE_DIR}/targets/${ext})
+      set(include_statements_var
+          "${include_statements_var}#include \"backends/p4tools/modules/smith/targets/${ext}/register.h\"\n"
+      )
+      set(smith_targets_var "${smith_targets_var}    ${ext}RegisterSmithTarget();\n")
+    endif()
+  endif()
+endforeach(ext)
+
+# Fill the template
+configure_file(register.h.in register.h)
+
+add_library(smith ${SMITH_SOURCES})
+target_link_libraries(smith
+  ${SMITH_LIBS}
+  # For Abseil includes.
+  PRIVATE frontend
+)
+
+add_dependencies(smith p4tools-common)
+
+add_p4tools_executable(p4smith main.cpp)
+
+target_link_libraries(
+  p4smith
+  PRIVATE smith
+  ${SMITH_LIBS}
+  PRIVATE ${P4C_LIBRARIES}
+  PRIVATE ${P4C_LIB_DEPS}
+)
+
+add_custom_target(
+  linkp4smith # Add some convenience links for invoking p4smith.
+  COMMAND ${CMAKE_COMMAND} -E create_symlink ${CMAKE_CURRENT_BINARY_DIR}/p4smith
+          ${CMAKE_BINARY_DIR}/p4smith
+)
+
+add_dependencies(p4smith linkp4smith)

backends/p4tools/modules/smith/README.md

@@ -0,0 +1,79 @@
+[![Status](https://github.com/p4lang/p4c/actions/workflows/ci-p4tools.yml/badge.svg)](https://github.com/p4lang/p4c/actions/workflows/ci-p4tools.yml)
+
+# <img src="https://p4.org/wp-content/uploads/2021/05/Group-81.png" width="40">P4Smith
+
+## Table of Contents
+
+- [Installation](#installation)
+- [Extensions](#extensions)
+- [Usage](#usage)
+- [Limitations](#limitations)
+- [Further Reading](#further-reading)
+- [Contributing](#contributing)
+- [License](#license)
+
+P4Smith is an extensible random P4 program generator in the spirit of [CSmith](https://en.wikipedia.org/wiki/Csmith). P4Smith generates random, but valid P4 programs for various P4 targets, for example the [v1model.p4](https://github.com/p4lang/behavioral-model/blob/main/docs/simple_switch.md) architecture on [BMv2](https://github.com/p4lang/behavioral-model) or `tna.p4` running on Tofino 1. P4Smiths generates programs that are valid according to the latest version of the (P4 specification)[https://p4.org/p4-spec/docs/P4-16-working-spec.html] or the restrictions of the specific target.
+
+## Installation
+
+P4Smith depends on the P4Tools framework and is automatically installed with P4Tools. Please follow the instructions listed [here](https://github.com/p4lang/p4c/tree/main/backends/p4tools#building) to install P4Smith. The main binary `p4smith` can be found in the `build` folder after a successful installation.
+
+P4Smith is available as part of the [official P4C docker image](https://hub.docker.com/r/p4lang/p4c/). On Debian-based systems, it is also possible to install a P4Smith binary by following [these](https://github.com/p4lang/p4c#installing-packaged-versions-of-p4c) instructions.
+
+## Extensions
+P4Smith extensions are instantiations of a particular combination of P4 architecture and the target that executes the P4 code. For example, the `v1model.p4` architecture can be executed on the behavioral model. P4Smith extension make use of the core P4Smith framework to generate programs. Several open-source extensions are available.
+
+### core.p4 using the test compiler p4test
+[targets/generic](targets/generic)
+
+This random program generator generates random packages and tries to produce all valid P4 code according to the latest P4 specification. Programs should be compiled using [p4test](https://github.com/p4lang/p4c/tree/main/backends/p4est).
+
+### v1model.p4 and psa.p4 on BMv2
+[targets/bmv2](targets/bmv2)
+
+P4Smith supports generating P4 programs for the `v1model` and `psa` architecture on [BMv2](https://github.com/p4lang/behavioral-model).
+
+### pna.p4 on the DPDK SoftNIC
+[targets/pna](targets/pna)
+
+The [DPDK-SoftNIC](https://github.com/p4lang/p4-dpdk-target) is a new target implemented using the [Data Plane Development Kit (DPDK)](https://www.dpdk.org/). The SoftNIC can be programmed using the P4 `pna.p4` architecture.
+
+### tna.p4 on Tofino 1
+[targets/ebpf](targets/ebpf)
+
+P4Smith can also generate programs for the `tna` architecture on Tofino 1.
+
+## Usage
+To access the possible options for `p4smith` use `p4smith --help`. To generate a test for a particular target and P4 architecture, run the following command:
+
+```bash
+./p4smith --target [TARGET] --arch [ARCH] prog.p4
+```
+Where `ARCH` specifies the P4 architecture (e.g., v1model.p4) and `TARGET` represents the targeted network device (e.g., BMv2). `prog.p4` is the name of the generated program.
+
+## Further Reading
+P4Smith was originally titled Bludgeon and part of the Gauntlet compiler testing framework. Section 4 of the [paper](https://arxiv.org/abs/2006.01074) provides a high-level overview of the tool.
+
+
+If you would like to cite this tool please use this citation format:
+```latex
+@inproceedings{ruffy-osdi2020,
+author = {Ruffy, Fabian and Wang, Tao and Sivaraman, Anirudh},
+title = {Gauntlet: Finding Bugs in Compilers for Programmable Packet Processing},
+booktitle = {14th {USENIX} Symposium on Operating Systems Design and Implementation ({OSDI} 20)},
+year = {2020},
+publisher = {{USENIX} Association},
+month = nov,
+ abstract = {
+  Programmable packet-processing devices such as programmable switches and network interface cards are becoming mainstream. These devices are configured in a domain-specific language such as P4, using a compiler to translate packet-processing programs into instructions for different targets. As networks with programmable devices become widespread, it is critical that these compilers be dependable. This paper considers the problem of finding bugs in compilers for packet processing in the context of P4-16. We introduce domain-specific techniques to induce both abnormal termination of the compiler (crash bugs) and miscompilation (semantic bugs). We apply these techniques to (1) the opensource P4 compiler (P4C) infrastructure, which serves as a common base for different P4 back ends; (2) the P4 back end for the P4 reference software switch; and (3) the P4 back end for the Barefoot Tofino switch. Across the 3 platforms, over 8 months of bug finding, our tool Gauntlet detected 96 new and distinct bugs (62 crash and 34 semantic), which we confirmed with the respective compiler developers. 54 have been fixed (31 crash and 23 semantic); the remaining have been assigned to a developer. Our bug-finding efforts also led to 6 P4 specification changes. We have open sourced Gauntlet at p4gauntlet.github.io and it now runs within P4C’s continuous integration pipeline.}
+}
+
+```
+
+## Contributing
+
+Contributions to P4Smith in any form are welcome! Please follow the guidelines listed [here](https://github.com/p4lang/p4c/blob/main/CONTRIBUTING.md) to contribute.
+
+## License
+
+This project is licensed under the Apache License 2.0. See the [LICENSE](https://github.com/p4lang/p4c/blob/main/backends/p4tools/LICENSE) file for details.