Vivado outputs garbled message - memory corruption?

[sbourdeauducq]

• Download https://m-labs.hk/sayma/vivado_6040.zip (this is the Verilog for Sayma AMC with SAWG)
• Run bash build_top.sh
• Vivado produces the following message

WARNING: [Synth 8-6040] Register ���_ driving address of a ROM cannot be packed in BRAM/URAM because of presence of initial value.

The name of the register is obviously incorrect and varies between runs, which can be a sign of memory corruption that might have more serious effects.

[sbourdeauducq]

Without mor1kx dependency: https://m-labs.hk/sayma/vivado_6040_nomor1kx.zip

[sbourdeauducq]

According to Xilinx tech support:
"The messaging bug in Vivado 2017.4 only affects the message itself, and not the resulting netlist coming from it. The netlist will be correct. The issue is due to the message receiving the pointer for the actual name, rather than just the actual name of the register, which is why the message looks so garbled. As Marc mentioned, this is corrected in the upcoming 2018.1 Vivado release."

[jbqubit]

Thanks for tracking this down @sbourdeauducq. Glad the conduit to Xilinx tech support is now open.