Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with compilation
Search options not deleted
user 6106
For questions regarding contracts compilation.
6
votes
2
answers
2k
views
What is the program counter at the start of an Ethereum method execution?
When a method in a deployed contract is called (either by an externally controlled account or by another smart contract), what will the program counter be at the beginning of the method call? In other …
- 18.7k
9
votes
Accepted
What is the program counter at the start of an Ethereum method execution?
The program counter is always 0 at the beginning of an execution. The contract sets the program counter to match the correct method call through a switch statement (a jump table) at the beginning of t …
- 18.7k
6
votes
Accepted
How are the arguments of the constructor encoded in the contract creation transaction?
According to the Ethereum Yellow Paper (section 4.2), the contract creation transaction does not have a data byte array where the arguments to method calls are placed. The contract creation only has t …
eth♦
- 86.5k
4
votes
1
answer
2k
views
How are the arguments of the constructor encoded in the contract creation transaction?
The Ethereum ABI defines how arguments are encoded and passed when a method is called. But how are the arguments to the constructor encoded in the contract creation transaction which creates the smart …
eth♦
- 86.5k
10
votes
Accepted
Why does compiled solidity code do this check on the argument with which it was called?
Code execution in EVM always starts with PC=0. So the method you have called is jumped to in a switch-like code segment in the beginning of the bytecode of the EVM.
CALLDATALOAD is not the argument g …
- 4,230
8
votes
1
answer
1k
views
Why does compiled solidity code do this check on the argument with which it was called?
I have compiled the following Solidity code:
pragma solidity ^0.4.9;
import "./Callee.sol";
contract Caller{
function call(address callee_address){
Callee callee = Callee(callee_address);
…
- 4,230