7055271...
by
Andy Fingerhut <email address hidden>
Remove unnecessary p4include/psa.p4 (#2837)
* Remove unnecessary p4include/psa.p4
It is no longer needed now that p4include/bmv2/psa.p4 and
p4include/dpdk/psa.p4 have been created, and each of those should be
used for their respective targets.
b3679a5...
by
Andy Fingerhut <email address hidden>
Minor updates to BMv2 and DPDK psa.p4 include files (#2838)
There is no reason for the psa.p4 include file to include core.p4,
given that it is recommended practice that every P4_16 PSA program
first include core.p4, then psa.p4.
Move const declarations in bmv2/psa.p4 later, after the types they use
have been declared.
Correct a URL in comments in bmv2/psa.p4
bmv2/psa.p4 should declare match_kind optional. It was already part
of the former p4include/psa.p4, but was not copied over into
p4include/bmv2/psa.p4
Remove comments from bmv2/psa.p4 that are either obsolete, or specific
to the BMV2 target.
Expand side-effect computations in table keys (#2805)
* Expand table keys with side-effects
df0ca8b...
by
Radostin Stoyanov <email address hidden>
Enable automatic release on version change (#2829)
* Use version file
This commit create a VERSION file that can be used to obtain the current
version of P4C.
The current version string "1.2.0+g202103291035~a69e52" contains a semantic
version, date and current git commit. However, the date makes sense only in
packages. Building the same P4C compiler code on a different day should not
result in a different version name. The current git commit is automatically
from the git history.
This GitHub action doesn't create a release, it only tests if a static
build works on Ubuntu 20.04. Thus, using the name "static build" looks
more accurately describes what it does.
