We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
My fuzzer found a bug where ICE occurred when using --ir-ast-json or --ir-optimized-ast-json
I fed the .sol files in the test/libsolidity directory into my fuzzer as the initial corpus, and it found this bug
the code
contract Test { function f() public pure returns (string memory) { return type(C).name; } function g() public pure returns (string memory) { return type(A).name; } function h() public pure returns (string memory) { return type(I).name; } } abstract contract A { function f() virtual public pure; } interface I { function f() external pure; } contract C { function f() pure public { } }
the cmd
solc --ir-ast-json a.sol # or solc --ir-optimized-ast-json a.sol
the bug
Internal compiler error: /solidity/libsolidity/interface/CompilerStack.cpp(821): Throw in function solidity::yul::YulStack solidity::frontend::CompilerStack::loadGeneratedIR(const string&) const Dynamic exception type: boost::wrapexcept<solidity::langutil::InternalCompilerError> std::exception::what: Invalid IR generated: Error: Expected keyword "object". [solidity::util::tag_comment*] = Invalid IR generated: Error: Expected keyword "object".
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
My fuzzer found a bug where ICE occurred when using --ir-ast-json or --ir-optimized-ast-json
Environment
Steps to Reproduce
I fed the .sol files in the test/libsolidity directory into my fuzzer as the initial corpus, and it found this bug
the code
the cmd
solc --ir-ast-json a.sol # or solc --ir-optimized-ast-json a.sol
the bug
The text was updated successfully, but these errors were encountered: