On Sun, Jan 3, 2010 at 9:15 AM, Jason Dusek wrote:
>
> I would like to know how the `__global_clock' influences
> execution in the present system.
As you observed, __global_clock is no longer used for rule scheduling.
It is only there to provide a time reference. BTW, __global_clock is
access
I am mystified by the relationship between Atom's
`__global_clock' and the `scheduling_clock'. For example, here
is some generated code:
/* Includes omitted. */
static uint64_t __global_clock = 0;
/* Subroutine declarations omitted. */
void main(void) {
{
sta
