<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Synthesis on Sigasi</title><link>https://www.sigasi.com/tags/synthesis/</link><description>Recent content in Synthesis on Sigasi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 15 Oct 2012 00:00:00 +0000</lastBuildDate><atom:link href="https://www.sigasi.com/tags/synthesis/index.xml" rel="self" type="application/rss+xml"/><item><title>VHDL Physical Type is not Synthesizable, or is it? (part 2)</title><link>https://www.sigasi.com/tech/vhdl-physical-type-not-synthesizable-or-it-part-2/</link><pubDate>Mon, 15 Oct 2012 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/vhdl-physical-type-not-synthesizable-or-it-part-2/</guid><description>&lt;p&gt;In a previous post, &lt;a href="https://www.sigasi.com/tech/vhdl-physical-type-not-synthesizable-or-it/"&gt;VHDL Physical Type is not Synthesizable, or is it?&lt;/a&gt;, I pointed out that VHDL synthesis tools can indeed synthesize VHDL physical types. In the example I gave, all computations with physical types were done at elaboration time, so that the synthesis tool does not really have to deal with physical types at all.&lt;/p&gt;</description></item><item><title>VHDL Physical Type is not Synthesizable, or is it?</title><link>https://www.sigasi.com/tech/vhdl-physical-type-not-synthesizable-or-it/</link><pubDate>Thu, 11 Oct 2012 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/vhdl-physical-type-not-synthesizable-or-it/</guid><description>&lt;p&gt;Everybody who has been taught VHDL in college or in a company with senior colleagues has heard the following &lt;em&gt;&amp;ldquo;wisdom&amp;rdquo;&lt;/em&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Pysical types are for simulation only. They cannot be synthesized.&lt;/em&gt;
[commonly heard claim – debunked in this article]&lt;/p&gt;</description></item><item><title>Clock edge detection</title><link>https://www.sigasi.com/tech/clock-edge-detection/</link><pubDate>Mon, 09 Apr 2012 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/clock-edge-detection/</guid><description>&lt;p&gt;There are two largely accepted ways to detect clock edges, and many style books prescribe or prefer one over the other.
Let&amp;rsquo;s investigate.&lt;/p&gt;
&lt;p&gt;This article deals with edge detection in &lt;em&gt;synthesizable&lt;/em&gt; code, not with behavioral code as found in testbenches and behavioral models.&lt;/p&gt;</description></item><item><title>VHDL Pragmas</title><link>https://www.sigasi.com/tech/vhdl-pragmas/</link><pubDate>Tue, 05 Apr 2011 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/vhdl-pragmas/</guid><description>&lt;p&gt;In VHDL, some tools support so-called &lt;em&gt;compiler directives&lt;/em&gt;. A compiler directive, or pragma is additional information that you give to the VHDL compiler (the simulator or synthesis tool). While your directive has no influence on the VHDL code itself, it changes the behavior. The IEEE, in their VHDL RTL standard, defines a pragma as &lt;em&gt;A generic term used to deﬁne a construct with no predeﬁned language semantics that inﬂuences how a synthesis tool will synthesize VHDL code into an equivalent hardware representation.&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>