instances reusing same absolute address?

[nachumg]

Currently the following compiles, and peakrdl_cheader incorrectly adds both reg_a and reg_b to the generated soc struct.

Should the compiler fail, since both reg_a and reg_b "reuse" the same absolute address?

reg reg_a_t {
  field {} f_a1;
};
reg reg_b_t {
  field {} f_b1;
};
addrmap soc {
  reg_a_t reg_a @0x100;
  reg_a->ispresent = false;
  reg_b_t reg_b @0x100;
};

[amykyta3]

Something doesn't seem right.
When I generate the header using the above input, I see the correct output: The header only contains reg_b, and reg_a is skipped.

Is it possible you are using a modified version of PeakRDL-cheader that ignores the ispresent property?

[nachumg]

Correct.
We added a customization to emit placeholders for not-ispresent components.
We are mistakenly doing that when there is reuse of an absolute address.