Re: weird block on Get from basic protected bounded buffer with 2 tasks

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2017-12-12 20:08, George Shapovalov wrote:

> I thought might be prioritizing Gets would make it behave

Then the barrier must be

    Count = 0 or else (Count < maxCount and then Get'Count = 0)

i.e. empty or else not full and no pending Get.

BTW, prioritizing is a bad idea. If you enforce entry order you also 
increase possibility of context switches upon bulk buffer updates. If 
one task makes several Puts and another does several Gets over an empty 
buffer you may end up switching these tasks for each Put/Get pair. Which 
defeats the very purpose of buffering. That is for a single core. For 
multiple cores prioritizing would have no sense at all.

> So, what gives? Am I missing something here or is this a bug?
> 
> The used platform: Gentoo Linux, gnat-gpl-2017, gcc-6.3.0

On some older platforms tasking must be kicked on, if I correctly 
remember. E.g. by beginning the main with

    delay 0.0;

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de