UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Explorer
Explorer
520 Views
Registered: ‎11-23-2009

[Synth 8-3332] gone in Vivado 2018.3

I have a scripted build flow which works nicely for a range of projects and a quite wide range of vivado versions, currently the 2017.2 to 2018.3. For 2018.2 and before I often got warnings

   WARNING: [Synth 8-3332] Sequential element (xxx) is unused and will be removed from yyy.

For 2018.3, with an identical build script, I do not see any [Synth 8-3332] messages.

I found the [Synth 8-3332] warnings often useful and thus wonder what happened.
Was that type of warning removed ? If yes, why ?
Or must it be explicitly enabled ?

Thanks in advance for any hint/help,  Walter

0 Kudos
3 Replies
Moderator
Moderator
460 Views
Registered: ‎03-16-2017

Re: [Synth 8-3332] gone in Vivado 2018.3

Hi @wfjmueller,

DId you check that in Vivado 2018.3 those sequential elements are present or not Which were removed in earlier Vivado versions?

 

If yes, then can you provide a small testcase to check this difference in mulitple Vivado versions at my end? 

Regards,
hemangd

Don't forget to give kudos and mark it as accepted solution if your issue gets resolved.
0 Kudos
Explorer
Explorer
424 Views
Registered: ‎11-23-2009

Re: [Synth 8-3332] gone in Vivado 2018.3

Hi @hemangd,

find attached two projects. Identical sources, one 2017.2 and one 2018.3 project with synthesis step run.

For 2017.2 one gets
   Synth 8-6014
   Synth 8-3331
   Synth 8-3332

For 2018.3 one gets
   Synth 8-6014
   Synth 8-3331 
   Constraints 18-5210

--> Synth 8-3332 warnings are gone.

0 Kudos
Explorer
Explorer
351 Views
Registered: ‎11-23-2009

Re: [Synth 8-3332] gone in Vivado 2018.3

Hi @hemangd,

did somebody have a look at the example cases ? The elements marked as removed in 2017.2 are indeed not used, e.g. because an input is constant. Can easily happen when a module is instanciated but not all functionality is used by the parent. Nevertheless, I always check (via a message filter) what is removed and whether that changes, and this more than once alerted me to little stupid errors. So I'd like to have the 3332 message back.

 

0 Kudos