Xilinx

Vivado

Vivado has a single warning format, but two different type of warnings: critical warnings and non critical warnings. Some warning messages can also span multiple lines.

Critical Warnings

Warnings with IDs are identified with the Warning keyword and the ID between colons. The message is after the second colon.

where:

Item	Regular Expression Match
warning keyword	^CRITICAL WARNING
ID	\W+sW+
message	.*$

Non Critical Warnings

Non critical warnings are identical to critical warnings except the keyword.

where:

Item	Regular Expression Match
warning keyword	^WARNING
ID	\W+sW+
message	.*$

Multiline Warnings

Multiline warnings can span any number of lines. They are identified with at least on space at the beginning of the line for each line after the initial warning line.

where:

Item	Regular Expression Match
warning keyword	^[WARNING\|CRITICAL WARNING]
ID	\W+sW+
message1	.*$
warning continuation	^s+
message2	.*$
message3	.*$

Extracting Warnings

Extraction of warnings from the logfile will follow this process:

Search for lines starting with WARNING or CRITICAL WARNING
Extract ID and message
Check successive lines for line beginning with spaces

append line to existing message

Vivado Methodology

The Vivado methologoy report has a single warning format, but two different type of warnings: critical warnings and non critical warnings. Some warning messages can also span multiple lines.

Methodology Format

Each methodology violation is reported over multiple lines.

<ID>#<count> <classification> <description> <details> Related violations: <related>

where:

Item	Regular Expression Match
ID	W+
count	[0-9]+
classification	W+
details	\W+sW+
related	\W+sW+

Extracting Warnings

Extraction of warnings from the logfile will follow this process:

Search for second line starting with 2. REPORT DETAILS
Extract ID and drop count and classification
drop description
Extract details
drop related