Re: gEDA: Icarus 0.6.1 / 0.5

[Ales Hvezda <ahvezda-at-NOSPAMseul_dot_org>]

[ Ales here, I'm reposting this since majordomo didn't recognize the
  e-mail as being subscribed to the geda-dev mailinglist. ]

-- Cut here --

A couple things. There was a scheduling change in .6 to .6.1 that may be 
the culprit, but at the same time - comparing 0.6.1 and Verilog XL gets 
the same result!  

I would point out that the coding style lends itself to races all over 
the place. Things might very simply change due to what gets evaluated 
first within the assign statements (Verilog makes no guarantees here..) 
I'll leave it to Mr. Williams to explain what he changed in
scheduling - but it gives better answers than we were getting a couple 
weeks ago. That
much I'm certain of.

Steve Wilson



Ales Hvezda wrote:

>[ Ales here, I'm reposting this since majordomo didn't recognize the
>  e-mail as being subscribed to the geda-dev mailinglist.  I'm also trying
>  for the first time in a while to actually forward an attachement, so let
>  me know if you can't read the attachement.]
>
>-- Cut here --
>From: "Sarfraz Nawaz" <siffi28@hotmail.com>
>
>Hi,
>I've been using Icarus 0.5 on Slackware 8 and on RedHat 6.1 for some time. I 
>recently upgraded to 0.6.1 on Slackware 8 and noticed that it isn't 
>producing correct results for my register with parallel load composed of -ve 
>edge triggered D flip flops. I'm attaching a tar file that contains a 
>register.v (verilog code) and a output file which contains the outputs both 
>from 0.6.1 and 0.5 .
>I'm curious that is it some bug in 0.6.1 or am I doing something wrong.
>Thanks for your time.
>Regards
>