Closed qbzzt closed 3 years ago
not realy I don't. I just send code to lllc tool and get the feedback.
lllc --help
Usage lllc [OPTIONS] <file>
Options:
-b,--binary Parse, compile and assemble; output byte code in binary.
-x,--hex Parse, compile and assemble; output byte code in hex.
-a,--assembly Only parse and compile; show assembly.
-t,--parse-tree Only parse; show parse tree.
-o,--optimise Turn on/off the optimiser; off by default.
-d,--disassemble Disassemble input into an opcode stream.
-h,--help Show this help message and exit.
-V,--version Show the version and exit.
Does retesheth
run lllc
once per test, or once per contract? If the second, then you know whether it failed when you were running it for contract 0x00..0100
, 0xcc...ccccc
, etc.
Works great with the first line. Thank you.
When a test includes LLL code (which is the vast majority of them) and LLC fails we sometimes get an uninformation message. In those cases it would be useful to know what contract's compilation failed, information that retesteth should already have.