Compiler Bug

[maliangyi]

According to the guidelines， I run "p4c-analysis ./running-integrated.p4". However，an exception was thrown. Is this a bug？
the running log as follow:

root@f977923405de:/bf4-master/sigcomm-2020/running_example# python3 ../cleanup_v1.py -o . running.p4
['p4c-bm2-ss', '--std', 'p4-16', '--make-field-lists', './running-clean.p4', 'running.p4']
cleaned up running.p4 -> ./running-clean.p4. Validating...
done instrumentation in 292ms
done primitive expansion in 409ms
done integration in 445ms
All set. To run bf4:
p4c-analysis ./running-integrated.p4
root@f977923405de:/bf4-master/sigcomm-2020/running_example# p4c-analysis ./running-integrated.p4
starting frontend
./running-integrated.p4(17): [--Wwarn=unknown] warning: Unknown annotation: readonly
extern void copyPacket(mutable_packet self, @readonly mutable_packet other);
^^^^^^^^
./running-integrated.p4(33): [--Wwarn=unknown] warning: Unknown annotation: matchKind
@matchKind("lpm")
^^^^^^^^^
./running-integrated.p4(39): [--Wwarn=unknown] warning: Unknown annotation: controlled
@Controlled extern flow_def_ipv4_lpm_0 query_ipv4_lpm_0(@matchKind("lpm") in bit<32> ipv4_lpm_0_ipv4_dstAddr);
^^^^^^^^^^
/usr/local/share/p4c/p4include/v1model.p4(31): [--Wwarn=unknown] warning: Unknown annotation: metadata
@metadata @name("standard_metadata")
^^^^^^^^
/usr/local/share/p4c/p4include/v1model.p4(59): [--Wwarn=unknown] warning: Unknown annotation: alias
@alias("queueing_metadata.enq_timestamp")
^^^^^
/usr/local/share/p4c/p4include/v1model.p4(442): [--Wwarn=unknown] warning: Unknown annotation: pipeline
@pipeline
^^^^^^^^
/usr/local/share/p4c/p4include/v1model.p4(460): [--Wwarn=unknown] warning: Unknown annotation: deparser
@deparser
^^^^^^^^
./running-integrated.p4(401): [--Wwarn=unknown] warning: Unknown annotation: noreturn
@impl("parse_and_run_") @NoReturn extern void parse_and_run(mutable_packet pin, inout metadata metas_, inout standard_metadata_t standard_meta);
^^^^^^^^
frontend done in 656ms
done unrolling 0 67 in 0ms
done graph buildup 1344 in 37ms, linking in 2ms
done chaotic iterations 1344, iters: 1360 in 20 ms
done constant propagation #nodes:1344 #vars:578 in 67ms
done constant propagation and simplification #nodes:1344 vs 679 #foldings:205 in:85ms
done unrolling 0 679 in 2ms
In file: /bf4-master/backends/analysis/context/InterproceduralCFGs.cpp:61
Compiler Bug: reached root node end: but no method set

[dragosdmtrsc]

Hi, can you please try updating to the latest commit?

[NofelYaseen]

I was getting something similar. This is how I got it work.
Assuming bf4 is compiled.

cd bf4/build
mv bf4/sigcomm-2020/running_example/running.p4 .
make cptemplate
python3 ../sigcomm-2020/cleanup_v1.py running.p4
p4c-analysis running-integrated.p4

If you are not in build folder, it probably won't work.

[maliangyi]

Thanks. It works well.
In addition, I have another question. In the P4 syntax, there are operations to add and remove headers, which affect the processing logic of subsequent entries and the result of the decision. For example, if the upstream table's action adds a header, the downstream entry can use it without check. If check the downstream table bf4, an uninitialized header error will be occurring. However, there is no such uninitialized problem in practice.

[NofelYaseen]

Please post a sample program.