Hi Again,
This email is a very long rabbit-hole into formal verification itself -
If you don't really care about this - just about QA and CI integration,
then you can skip this mail entirely - I will send an update on that in
a few days.
If you would like to help out with the verification run, th
> Mathew, Cherry G * writes:
[...]
> With that thought, I take leave for the weekend, and hope to put
> my money where my mouth is, by debugging the current C
> implementation using ideas described above.
> $ make prog $ ./arc
> should give you a crash dump for gdb, w
> Mathew, Cherry G * writes:
> Mathew, Cherry G * writes:
> [...]
>> The next step is to write the equivalent C code, compile it with
>> a simple test "driver" (ideally ATF, but since this is standalone
>> for the moment, I'll use something simpler, just to illustrate
> Mathew, Cherry G * writes:
[...]
> The next step is to write the equivalent C code, compile it with a
> simple test "driver" (ideally ATF, but since this is standalone
> for the moment, I'll use something simpler, just to illustrate the
> concept), and then hook it into s
> Mathew, Cherry G * writes:
[...]
> So there's room for improvement in my Makefile to:
> 1) Explore multithreaded/CPU
> 2) Understand state space explosion scale - it is exponential to
> the number of processes, I've fixed it to run in a loop - will
> report back once
5 matches
Mail list logo
