<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mythbuster on Sigasi</title><link>https://www.sigasi.com/tags/mythbuster/</link><description>Recent content in Mythbuster on Sigasi</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 19 Feb 2026 14:25:38 +0100</lastBuildDate><atom:link href="https://www.sigasi.com/tags/mythbuster/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/legacy/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/legacy/tech/vhdl-physical-type-not-synthesizable-or-it-part-2/</guid><description>&lt;p>In a previous post, &lt;a href="https://www.sigasi.com/legacy/tech/vhdl-physical-type-not-synthesizable-or-it/">VHDL Physical Type is not Synthesizable, or is it?&lt;/a>, 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></description></item><item><title>VHDL Physical Type is not Synthesizable, or is it?</title><link>https://www.sigasi.com/legacy/tech/vhdl-physical-type-not-synthesizable-or-it/</link><pubDate>Thu, 11 Oct 2012 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/legacy/tech/vhdl-physical-type-not-synthesizable-or-it/</guid><description>&lt;p>Everybody who has been taught VHDL in college or in a company with senior colleagues has heard the following &lt;em>&amp;ldquo;wisdom&amp;rdquo;&lt;/em>:&lt;/p>
&lt;blockquote>
&lt;p>&lt;em>Pysical types are for simulation only. They cannot be synthesized.&lt;/em>
[commonly heard claim – debunked in this article]&lt;/p></description></item><item><title>VHDL case statements can do without the "others"</title><link>https://www.sigasi.com/tech/vhdl-case-statements-can-do-without-others/</link><pubDate>Mon, 24 Oct 2011 00:00:00 +0000</pubDate><guid>https://www.sigasi.com/tech/vhdl-case-statements-can-do-without-others/</guid><description>&lt;p>I was talking to some engineering students the other day, as they were doing a VHDL lab. I noticed a VHDL case statement for state machine with named states (enumerated data type). All states were handled in their VHDL case statement, and still they put an &lt;code>others&lt;/code> section in their code. I had a hard time explaining that this clause was useless. The students mumbled something about their professor eating them alive if they&amp;rsquo;d forget the &lt;code>others&lt;/code> and problems with uninitialized stated and high-impedance state. As you might know, these concepts are related to the &lt;code>std_ulogic&lt;/code> and &lt;code>std_logic&lt;/code> type, but not to enumerated types.&lt;/p></description></item></channel></rss>