Re: [Gems-users] Checking new protocol

[Blas Cuesta <blacuesa@xxxxxxxxxx>]

I have some questions about the random tester. 

- Is there any manual for the random tester? How does it work? Does it need 
any configuration file?

- On what is the random tester based to check the correctnes of the protocols? 
I mean, I would like to know if it uses some generated code from the slicc 
files (for example, funtions like getState or setState) or, otherwise, it 
only checks that requests are eventually satisfied in a finite period of 
time. I want to know that, because the code that runs my modified simulator 
is not the same than the generated code from the slicc files. I have done 
some changes in the generated files because of slicc limitations.

Thanks.

Best regards,

Blas.


>The random tester is designed to stress-test the correctness of the
>protocols.  It catches many errors, but does not have 100% coverage.
>
>--Mike
>
>
>Blas Cuesta wrote:
>> Hello!
>>
>> I have done some modifications in the Token Coherence protocol 
>implementation
>> and I would like to check if these changes are correct. Is there any way to
>> check it? I run some simulations and, If any of them does not fail, I 
>suppose
>> the changes are correct. Could anyone tell me if there is another more
>> reliable method?
>>
>> Thanks,
>>
>> Blas.
>> _______________________________________________
>> Gems-users mailing list
>> Gems-users@xxxxxxxxxxx
>> https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>>

_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users