doc: remove note about --match-algod-bytecode

algorandfoundation · Nov 7, 2024 · 4fa8479 · 4fa8479
1 parent 9da41a0
commit 4fa8479
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 8 deletions.
diff --git a/docs/compiler.md b/docs/compiler.md
@@ -115,7 +115,6 @@ puyapy [-h] [--version] [-O {0,1,2}]
 | `--output-arc32`, `--no-output-arc32`                    | Output {contract}.arc32.json ARC-32 app spec file if the contract is an ARC-4 contract                                                                                | `True`                  |
 | `--output-client`, `--no-output-client`                  | Output Algorand Python contract client for typed ARC4 ABI calls                                                                                                       | `False`                 |
 | `--output-bytecode`, `--no-output-bytecode`              | Output AVM bytecode                                                                                                                                                   | `False`                 |
-| `--match-algod-bytecode` | When outputting bytecode  (via `--output-bytecode` or compiled programs), ensure bytecode matches algod output, by disabling additional optimizations | False   |
 | `--out-dir OUT_DIR`                                      | The path for outputting artefacts                                                                                                                                     | Same folder as contract |
 | `--log-level {notset,debug,info,warning,error,critical}` | Minimum level to log to console                                                                                                                                       | `info`                  |
 | `-g {0,1,2}`, `--debug-level {0,1,2}`                    | Output debug information level<br /> `0` = No debug annotations <br /> `1` = Output debug annotations <br /> `2` = Reserved for future use, currently the same as `1` | `1`                     |

diff --git a/docs/lg-compile.md b/docs/lg-compile.md
@@ -7,13 +7,6 @@ Once compiled, this bytecode can be utilized to construct AVM Application Call t
 
 The `--output-bytecode` option can be used to generate `.bin` files for smart contracts and logic signatures, producing an approval and clear program for each smart contract.
 
-```{note}
-The Puya compiler incorporates several optimizations that are not present in the bytecode output generated by the 
-[`/v2/teal/compile`](https://developer.algorand.org/docs/rest-apis/algod/#post-v2tealcompile) endpoint.
-When comparing the outputs of PuyaPy and Algod these differences may be observed. 
-To disable these optimizations and produce bytecode identical to Algod use the `--match-algod-bytecode` option.  
-```
-
 ## Obtaining bytecode within other contracts
 
 The [`compile_contract`](#algopy.compile_contract) function takes an Algorand Python smart contract class and returns a [`CompiledContract`](#algopy.CompiledContract),