Hi,
As per Mentor Graphics cookbook, under coding guidelines, it is recommended not to use filed automation macros. Using this macros not only cost simulation cycles but may also lead to unexpected behavior.
Is this issue resolved/addressed in latest UVM 1.1d ?
The recommendations of the Cookbook apply to all versions of UVM.
The recommendations for using field automation macros are independent of the UVM version.
Macros in general are nothing but abbreviated code which eventually get expanded. Hence they do impact the simulation efficiency, the scale of which depends of the size of the design and the testbench. And sometimes it may be difficult to debug any problem caused by a macro. I personally feel, testbench code should be simple to understand, not only for the developer, but also for the teams which would eventually use/re-use that code. Methodology experts do not recommend the usage of field automation macros. Instead it is better to write your own methods for copying, cloning, printing etc. on a need basis, so you know exactly what is happening. Also your code becomes much lighter in weight. Another flip-side to using field automation macros is - in case you forget to register a particular variable or two, all you convenience methods would start omitting those variables, and it would take you quite some time to figure that out.