Interpreting macro names in RTL

Question

I was wondering if someone could help me understand the macro naming in the RTL.
e.g.,
mcu_readdp_dp_msff_macro__stack_66c__width_65
mcu_readdp_dp_and_macro__ports_2__stack_1l__width_1
mcu_readdp_dp_nand_macro__ports_4__width_1
mcu_readdp_dp_nor_macro__dnor_4x__ports_3__width_1
mcu_readdp_dp_nor_macro__ports_3__width_1
I think I understand width, ports and the transistor sizing (4x) parameters.
Could someone help me with the stack parameter? On a related note,
how is this info passed on to the synthesis tool? The implementation
of the macros seem to use the same underlying module irrespective of the
parameters. For instance, both the nor macros above instantiate the same
'nor3' module.

Answer 1

AI doesn't even retain its own layer/ sub-layer/ group names after shuffling stuff around, so take a guess how likely it would be to achieve what you want. Or in otehr words: Unless the PDF was created from AI and has the editable data attached, this is very much a hopeless case. And I'm not sure if your sideway use of layers in ID is a good way of managing your data to begin with. I think you're trying to see something in them that they aren't. They're not per se "layout layers", but rather just a secondary meta structure for versioning or multi-language docs to define specific dependencies. Otherwise ID isn't much different from AI - it uses arranged objects and doesn't care about a strict layer metaphor or stacking. As long as it gives the desired appearance, it will group and arrange objects in whatever ways you fancy and that is defined on the per-object level as a property of the object, not a document layer or something...
Mylenium