<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Hierarchy and Isomorphism in Fast-SPICE simulators</title>
	<atom:link href="http://synopsysoc.org/analoginsights/?feed=rss2&#038;p=35" rel="self" type="application/rss+xml" />
	<link>http://synopsysoc.org/analoginsights/2008/02/hierarchy-and-isomorphism-in-fast-spice-simulators/</link>
	<description></description>
	<lastBuildDate>Thu, 04 Feb 2010 14:13:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Demler</title>
		<link>http://synopsysoc.org/analoginsights/2008/02/hierarchy-and-isomorphism-in-fast-spice-simulators/comment-page-1/#comment-515</link>
		<dc:creator>Mike Demler</dc:creator>
		<pubDate>Thu, 14 Feb 2008 19:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://synopsysoc.org/analoginsights/?p=35#comment-515</guid>
		<description>&lt;!-- Generated by XStandard version 2.0.0.0 on 2008-02-14T11:28:20 --&gt;

&lt;p&gt;Hi Jonathan,&lt;/p&gt;
&lt;p&gt;Yes! The top priorities expressed by users are to simulate faster, bigger... (and always cheaper - UGH!). You can add ease-of-use to that as well, which is somewhat more subjective but includes the language compatibility issues that you mentioned. Unfortunately, marketers have a bad habit of trying to create false and irrelevant differentiation by attacking how a competing tool gets there, rather than focusing on the end result and what users really need. Hence my reaction to those who would assert that hierarchy or some other technique that delivers real tangible benefit to the user is a bad thing. As I said in my earlier post... that is &lt;a href=&quot;http://synopsysoc.org/analoginsights/?p=16&quot; rel=&quot;nofollow&quot;&gt;Red Herring&lt;/a&gt; propaganda, and is not the least bit beneficial to users.&lt;/p&gt;
&lt;p&gt;I am especially interested in your last comment: &quot;&lt;em&gt;&lt;strong&gt;Don&#039;t expect me to use a different verification language for extracted transistor level simulation than I use for the rest of my functional verification&lt;/strong&gt;&lt;/em&gt;&quot;. You and I have talked about that for a bit in person, but if you have the time to expand on the topic here it would be very valuable. How would you like to see the functional verification capabilities of System Verilog VMM (for example) extended to include mixed-signal blocks down to the transistor level?&lt;/p&gt;
&lt;p&gt;-Mike&lt;br /&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p><!-- Generated by XStandard version 2.0.0.0 on 2008-02-14T11:28:20 --></p>
<p>Hi Jonathan,</p>
<p>Yes! The top priorities expressed by users are to simulate faster, bigger&#8230; (and always cheaper &#8211; UGH!). You can add ease-of-use to that as well, which is somewhat more subjective but includes the language compatibility issues that you mentioned. Unfortunately, marketers have a bad habit of trying to create false and irrelevant differentiation by attacking how a competing tool gets there, rather than focusing on the end result and what users really need. Hence my reaction to those who would assert that hierarchy or some other technique that delivers real tangible benefit to the user is a bad thing. As I said in my earlier post&#8230; that is <a href="http://synopsysoc.org/analoginsights/?p=16" rel="nofollow">Red Herring</a> propaganda, and is not the least bit beneficial to users.</p>
<p>I am especially interested in your last comment: &quot;<em><strong>Don&#8217;t expect me to use a different verification language for extracted transistor level simulation than I use for the rest of my functional verification</strong></em>&quot;. You and I have talked about that for a bit in person, but if you have the time to expand on the topic here it would be very valuable. How would you like to see the functional verification capabilities of System Verilog VMM (for example) extended to include mixed-signal blocks down to the transistor level?</p>
<p>-Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jonathan</title>
		<link>http://synopsysoc.org/analoginsights/2008/02/hierarchy-and-isomorphism-in-fast-spice-simulators/comment-page-1/#comment-505</link>
		<dc:creator>jonathan</dc:creator>
		<pubDate>Thu, 14 Feb 2008 16:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://synopsysoc.org/analoginsights/?p=35#comment-505</guid>
		<description>Hierarchy and Isomorphism are fine techniques, don&#039;t get me wrong. 
In my experience us users don&#039;t really care Which techniques the simulator uses. We just want SPEED, ACCURACY, Capacity.. 
and support for decent design languages, meaning (to me)
spice/spectre (to support existing netlisters/ extractors)
+ Verilog(all flavors) + VHDL(all flavors) (for sources/sinks and behavioral elements + some  verification wrappers and digital/analog/rf interface
+ verification language support ie PLI,e,SystemVerilog etc. (for my assertions etc)

Don&#039;t expect me to use a different verification language for extracted transistor level simulation than I use for the rest of my functional verification.</description>
		<content:encoded><![CDATA[<p>Hierarchy and Isomorphism are fine techniques, don&#8217;t get me wrong.<br />
In my experience us users don&#8217;t really care Which techniques the simulator uses. We just want SPEED, ACCURACY, Capacity..<br />
and support for decent design languages, meaning (to me)<br />
spice/spectre (to support existing netlisters/ extractors)<br />
+ Verilog(all flavors) + VHDL(all flavors) (for sources/sinks and behavioral elements + some  verification wrappers and digital/analog/rf interface<br />
+ verification language support ie PLI,e,SystemVerilog etc. (for my assertions etc)</p>
<p>Don&#8217;t expect me to use a different verification language for extracted transistor level simulation than I use for the rest of my functional verification.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
