8000 tc / ebpf backends use unparsed annotations · Issue #5021 · p4lang/p4c · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
tc / ebpf backends use unparsed annotations #5021
New issue
New issue
Open
Open
tc / ebpf backends use unparsed annotations#5021
Labels
ebpfTopics related to the eBPF back endgood-first-issueAn issue that could be solved by someone new to the code base.p4tcTopics related to the P4-TC back end. On PRs, also triggers p4tc CI tests to run.
@asl

Description

@asl
asl
opened on Nov 19, 2024

There should never be unparsed annotations actually used in the compiler -- it is just a matter of adding one PARSE_type line to parseAnnotations.cpp (or in a backend file). This is related to the mess that is "structured" annotations -- all annotations are structured -- it is just that some people didn't want to enumerate all the annotations in parseAnnotations.cpp as that was too hard to maintain.

Originally posted by @ChrisDodd in #5018 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    ebpfTopics related to the eBPF back endgood-first-issueAn issue that could be solved by someone new to the code base.p4tcTopics related to the P4-TC back end. On PRs, also triggers p4tc CI tests to run.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
      0