From c217bc2dcaf9deec38a54cc094b09288e95ba58f Mon Sep 17 00:00:00 2001 From: Alex Beregszaszi Date: Thu, 2 Feb 2017 21:33:46 +0000 Subject: Updated EVM output --- docs/using-the-compiler.rst | 29 ++++++++++++++++------------- 1 file changed, 16 insertions(+), 13 deletions(-) (limited to 'docs') diff --git a/docs/using-the-compiler.rst b/docs/using-the-compiler.rst index 3282b85a..2d78d58a 100644 --- a/docs/using-the-compiler.rst +++ b/docs/using-the-compiler.rst @@ -204,22 +204,25 @@ Output Description abi: [], evm: { assembly: - bytecode: - runtimeBytecode: + // Bytecode and related details. + bytecode: { + // The bytecode as a hex string. + object: "00fe", + // The source mapping as a string. See the source mapping definition. + sourceMap: "", + // If given, this is an unlinked object. + linkReferences: { + "libraryFile.sol": { + // Byte offsets into the bytecode. Linking replaces the 20 bytes located there. + "Library1": [1, 200, 80] + } + } + } + // The same layout as above. + deployedBytecode: { }, opcodes: annotatedOpcodes: // (axic) see https://github.com/ethereum/solidity/issues/1178 gasEstimates: - sourceMap: - runtimeSourceMap: - // If given, this is an unlinked object (cannot be filtered out explicitly, might be - // filtered if both bytecode, runtimeBytecode, opcodes and others are filtered out) - linkReferences: { - "sourceFile.sol:Library1": [1, 200, 80] // byte offsets into bytecode. Linking replaces the 20 bytes there. - } - // the same for runtimeBytecode - I'm not sure it is a good idea to allow to link libraries differently for the runtime bytecode. - // furthermore, runtime bytecode is always a substring of the bytecode anyway. - runtimeLinkReferences: { - } }, functionHashes: metadata: // see the Metadata Output documentation -- cgit