|
From: Stephen W. <st...@ic...> - 2009-02-23 20:16:48
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cary R. wrote: > --- On Mon, 2/23/09, Stephen Williams <st...@ic...> wrote: > >> That's a good point, although it may be a little bit >> tricky to >> implement. Hmm... > > My thought was some modification of elaborate_delay_expr(). > I believe all delays must be processed there so it is a > good single point to look for problems. You certainly need > some static state information and I have only thought about > this conceptually, so there may be other issues lurking in > the shadows. You have to look for all the places where the elaborator does timescale conversions. Sometimes the expression is non-constant and different code it invoked to do the scaling, but it may not be all that hard to find all the spots. - -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFJowQtrPt1Sc2b3ikRAlcKAKCZ+wiVi3yADWUnUDCLcjSj6fZXmQCg7cvT WGJ4cdPcR0S7wGBU0OnzNUo= =pP5/ -----END PGP SIGNATURE----- |