ProFoUnd Program Analysis Based Form Understanding Www2012

Instructions and help about ProFoUnd Program analysis Based Form Understanding Www2012

Now let's make sure that this program has all the properties we want. Namely, concurrency, absence of deadlock, and mutual exclusion of the important shared memory. Does it have concurrency? For this, we just need to convince ourselves that the critical sections of the code are short. This critical section here is just decrementing a variable and sending a signal. Not much work to be done there. And the tracker does the analogous thing. So we're okay on that front. The top two blocks, just this one and this one, these just check the condition and then call the wait procedure. And then they immediately unlock afterwards. So this also is short. Okay, so let's check off concurrency. The absence of deadlock, we can convince ourselves that both threads are never blocked. We can see that the mutex_lock can't be responsible for a deadlock because both the producer and consumer give up the lock writing after acquiring it, just as we argued about concurrency. There isn't much work to be done he