Prasanna T

The result may be a valid double precision value as we are doing single to double conversion.The main issue here is the derived nan-prefix (again why are we deriving nan-prefix?...

possibly the third one could be the issue, as i continue to investigate this. Can rule out the first two as the tests were passing through successfully on the `floating-point-dev`....

Found the same issue as @pcotret while running spike.

Would be nice if the sign is also represented in hex rather explicit sign as below for the hex values. inst_5:// rs1==x24, rd==f11, rs1_val == -1227077728 and rm_val == 0...

@pawks It's ready for review now...!

Found a new fix for this where we pass the value from `test.py` where we already compute `flen`. replacing `self.xlen` with below would fix the issue `list(testList.values())[0]['macros'][2].split("=")[1]`

``` coverage_cmd = 'riscv_isac --verbose info coverage -d \ -t {0}.log --parser-name c_sail -o coverage.rpt \ --sig-label begin_signature end_signature \ --test-label rvtest_code_begin rvtest_code_end \ -e ref.elf -c {1} -x{2} -f{3}...

Discussion Points on the ACT SIG (25 Aug 2022): This has to update in this template, @pawks agreed to make this change. Until then please use [this](https://gitlab.com/incoresemi/riscof-plugins/-/blob/fd-updates-sail-spike/sail_cSim/riscof_sail_cSim.py). @allenjbaum @pawks feel...