Add opcodes and opcodes_runtime flags to compiler

[iamdefinitelyahuman]

What I did

• added opcodes and opcodes_runtime flags to the compiler

How I did it

• added PUSH, SWAP and DUP opcodes to vyper/opcodes.py
• added new method get_opcodes to vyper/compiler.py
• added opcodes and opcodes_runtime to output_formats_map in vyper/compiler.py
• modified help string in bin/vyper

How to verify it

vyper -f opcodes examples/crowdfund.vy
vyper -f opcodes_runtime examples/crowdfund.vy

Description for the changelog

• added opcodes and opcodes_runtime flags to the compiler

Cute Animal Picture

[fubuloubu]

It would be nice to have a short test to show off how this works. (I'd love for it to be a doctest, and actually use them)

[jacqueswww]

LGTM, just fix the linting errors ;)

[jacqueswww]

@fubuloubu doc tests are great for a quick test suite, but in general I think it just adds too much clutter on a code base - especially since we have a very extensive test suite already.

[fubuloubu]

Doctests are nice because they keep the docs up to date

[iamdefinitelyahuman]

LGTM, just fix the linting errors ;)

oops!

[killersqueegie]

What's the difference between opcodes and opcodes_runtime?

[iamdefinitelyahuman]

• opcodes is generated from the bytecode used to deploy the contract
• opcodes_runtime is from the final deployed bytecode that is stored on-chain

If you are familiar with solc:

• opcodes is equivalent to evm.bytecode.opcodes
• opcodes_runtime is equivalent to evm.deployedBytecode.opcodes