<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recovering Parser on Sigasi</title><link>https://www.sigasi.com/tags/recovering-parser/</link><description>Recent content in Recovering Parser on Sigasi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 31 Jan 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sigasi.com/tags/recovering-parser/index.xml" rel="self" type="application/rss+xml"/><item><title>Recovering Verilog and SystemVerilog Parser</title><link>https://www.sigasi.com/tech/recovering-systemverilog-parser/</link><pubDate>Fri, 31 Jan 2020 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/recovering-systemverilog-parser/</guid><description>&lt;p&gt;When you&amp;rsquo;re writing HDL code, be it in SystemVerilog, Verilog or VHDL, your code is broken or incomplete most of the time.
Any regular compiler stops on the first error it encounters and will often only show an obscure error message.
At Sigasi, we are convinced productivity and happiness of HDL developers increase when they receive immediate feedback on broken code.&lt;/p&gt;</description></item><item><title>One mistake, one error marker</title><link>https://www.sigasi.com/legacy/tech/one-mistake-one-error-marker/</link><pubDate>Fri, 21 Sep 2012 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/legacy/tech/one-mistake-one-error-marker/</guid><description>&lt;p&gt;Ideally, if you make one mistake in VHDL, you want your compiler to show one error marker. Here is a small example.&lt;/p&gt;
&lt;p&gt;For this single mistake, Sigasi flags one error marker:
&lt;img src="https://www.sigasi.com/img/tech/recovering-vhdl-parser.png" alt="For this single mistake, Sigasi flags one error marker"&gt;
&lt;/p&gt;</description></item><item><title>Recovering VHDL Parser</title><link>https://www.sigasi.com/tech/recovering-vhdl-parser-0/</link><pubDate>Fri, 21 Sep 2012 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/recovering-vhdl-parser-0/</guid><description>&lt;p&gt;It is useful to analyze code that is only partly finished, code that still has errors in it. Analyzing broken code helps people understand, improve and complete the code. In order to perform such an analysis, you need a parser that recovers after it encounters an error. In the world of hardware design, hardly any recovering parsers exist and engineers are left out in the cold. All but a few EDA tools fail miserably at parsing incorrect VHDL code.&lt;/p&gt;</description></item><item><title>Three mistakes, three error markers</title><link>https://www.sigasi.com/tech/three-mistakes-three-error-markers/</link><pubDate>Fri, 21 Sep 2012 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/three-mistakes-three-error-markers/</guid><description>&lt;p&gt;Ideally, if you make three mistakes in VHDL, you want to see three error markers. Here is a small example.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://www.sigasi.com/img/tech/recovering-vhdl-parser-3errors.png" alt="Sigasi shows three error markers for these three errors"&gt;
&lt;/p&gt;
&lt;p&gt;A traditional VHDL compiler gives only one error message. You will have to fix this error and start the compiler again before you can find the next error. This takes extra time and you need all of your time you to work on complex design problems that you are dealing with.&lt;/p&gt;</description></item></channel></rss>