-
Notifications
You must be signed in to change notification settings - Fork 80
LDWG meeting minutes, May 6, 2019
- Antonin Bas (Barefoot)
- Gordon Brebner (Xilinx)
- Chris Dodd (Barefoot)
- Nate Foster (Cornell)
- Mihai Budiu (VMware)
- Andy Fingerhut (Cisco)
- Jed Liu (Barefoot)
-
Q: Are people using P4_16? A: Seems like yes.
-
What are our priorities?
-
Module system or some support for name spaces. This needs to be in the language and can't be bolted on.
-
Executable specifications for architectures
-
Events other packets
-
From Cisco meeting: What would P4++ look like?
- Some form of loops?
- Tagged unions?
-
Extensible parsers?
-
-
Target: v1.2 by end of the summer?
-
What happens when we run
cpp
? -
Do we run it separately on each file? Can
#include "defines.h"
in each file. Note that this preserves the current semantics. -
Need to clearly specify the semantics of
cpp
. -
For
import
, do we also wantfrom f import x as y
? -
Do we want to do conditional
imports
? -
Do we also want exports? And
export *
? -
Think about
@name
annotations and how they interact with module system. -
Should a module name be a file name or a path name?
-
Pull Request: https://github.com/p4lang/p4c/pull/1698
-
Action Item: interested parties should comment.
-
Pull Request: https://github.com/p4lang/p4c/pull/1859
-
Action Item: interested parties should comment.
- @cdodd will take a look and try to drive this proposal forward.
-
Pull Request: https://github.com/p4lang/p4-spec/issues/668
-
@jliu argues that slices should be unsigned
-
Action Item: Jed volunteers to change implementation to unsigned.
-
Pull Request: https://github.com/p4lang/p4-spec/issues/717
-
Action Item: @mbudiu-vmw to revise and we'll discuss in the future.
-
Pull Request: https://github.com/p4lang/p4c/issues/1914
-
Action Item: If an answer can be had for P4 Arch WG meeting on Wednesday, that would be ideal. @mbudiu-vmw to look.
- May 20th if @jafingerhut makes progress on namespace issue, otherwise June 3rd.