fix: Feature different frontend invocations

- ResNet example now features `torch_tensorrt.dynamo.compile`, while
transformers example features `torch_tensorrt.compile(...,
ir="dynamo_compile", ...)`

Author: gs-olive

examples/dynamo/dynamo_compile_resnet_example.py

@@ -36,7 +36,7 @@
 min_block_size = 3
 
 # Operations to Run in Torch, regardless of converter support
-torch_executed_ops = {}
+torch_executed_ops = {"torch.ops.aten.embedding.default"}
 
 # %%
 # Compilation with `torch_tensorrt.dynamo.compile`

examples/dynamo/dynamo_compile_transformers_example.py

@@ -47,9 +47,10 @@
 # ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 # Build and compile the model with torch.compile, using tensorrt backend
-optimized_model = torch_tensorrt.dynamo.compile(
+optimized_model = torch_tensorrt.compile(
     model,
-    inputs,
+    ir="dynamo_compile",
+    inputs=inputs,
     enabled_precisions=enabled_precisions,
     debug=debug,
     workspace_size=workspace_size,
@@ -59,7 +60,7 @@
 
 # %%
 # Equivalently, we could have run the above via the convenience frontend, as so:
-# `torch_tensorrt.compile(model, ir="dynamo_compile", inputs=inputs, ...)`
+# `torch_tensorrt.dynamo.compile(model, inputs, ...)`
 
 # %%
 # Inference