Skip to content

Commit ac47bcd

Browse files
Merge pull request #6 from pytorch-labs/refactor_website_markdown
[torch.compile Graph Break Website] Entire refactor of website to markdown files
2 parents e265109 + 01e4bea commit ac47bcd

File tree

239 files changed

+5143
-4597
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

239 files changed

+5143
-4597
lines changed

GBID directory/_config.yml

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Site settings
2+
title: Graph-Break Registry
3+
description: A registry of PyTorch Dynamo graph breaks.
4+
5+
# Base URL for the site
6+
# This is crucial for correct linking on GitHub Pages
7+
baseurl: "/docs/compile-graph-break" # Adjust this based on your actual GitHub Pages path
8+
9+
# Build settings
10+
theme: jekyll-theme-minimal # Or any other Jekyll theme you prefer
11+
remote_theme: pages-themes/minimal@v0.2.0 # For GitHub Pages remote theme
12+
plugins:
13+
- jekyll-remote-theme
14+
15+
# Exclude build-related files from Jekyll processing
16+
exclude:
17+
- node_modules
18+
- package.json
19+
- package-lock.json
20+
- generate-site.js
21+
- README.md
22+
- .gitignore
23+
- .github

GBID directory/gb/gb0000.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# GB0000
2+
3+
## Graph-Break Type
4+
*Short name describing what triggered the graph break*
5+
All __torch_function__ overrides returned NotImplemented due to TypeError from user code
6+
7+
## Context
8+
*Values or code snippet captured at the break point*
9+
fn={fn}, args={args}, kwargs={kwargs}
10+
11+
## Explanation
12+
*Why this specific graph break happened*
13+
All __torch_function__ overrides for for function {fn} returned NotImplemented
14+
15+
## Hints
16+
*Suggestions for fixing or working around the break*
17+
- Dynamo has detected that tracing the code will result in an error when running in eager. Please double check that your code doesn't contain a similar error when actually running eager/uncompiled.
18+
19+
20+
21+
[Back to Registry](../index.md)

GBID directory/gb/gb0001.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# GB0001
2+
3+
## Graph-Break Type
4+
*Short name describing what triggered the graph break*
5+
Argument of `as_subclass` must be a non-dispatcher-style tensor subclass
6+
7+
## Context
8+
*Values or code snippet captured at the break point*
9+
{self}.as_subclass({cls})
10+
11+
## Explanation
12+
*Why this specific graph break happened*
13+
Currently not supported
14+
15+
## Hints
16+
*Suggestions for fixing or working around the break*
17+
- Avoid this call or move it outside `torch.compile` regione
18+
- It may be possible to write Dynamo tracing rules for this code. Please report an issue to PyTorch if you encounter this graph break often and it is causing performance issues.
19+
20+
21+
22+
[Back to Registry](../index.md)

GBID directory/gb/gb0002.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# GB0002
2+
3+
## Graph-Break Type
4+
*Short name describing what triggered the graph break*
5+
Assertion failed on symbolic shapes
6+
7+
## Context
8+
*Values or code snippet captured at the break point*
9+
str(sym_expr)
10+
11+
## Explanation
12+
*Why this specific graph break happened*
13+
*No explanation provided.*
14+
15+
## Hints
16+
*Suggestions for fixing or working around the break*
17+
- Dynamo has detected that tracing the code will result in an error when running in eager. Please double check that your code doesn't contain a similar error when actually running eager/uncompiled.
18+
19+
20+
21+
[Back to Registry](../index.md)

GBID directory/gb/gb0003.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# GB0003
2+
3+
## Graph-Break Type
4+
*Short name describing what triggered the graph break*
5+
Attempt to trace generator
6+
7+
## Context
8+
*Values or code snippet captured at the break point*
9+
*No context provided.*
10+
11+
## Explanation
12+
*Why this specific graph break happened*
13+
Generators cannot be compiled directly with `torch.compile`.
14+
15+
## Hints
16+
*Suggestions for fixing or working around the break*
17+
- Call a generator from inside of a non-generator Python function and
18+
- compile that function instead.
19+
- This graph break is fundamental - it is unlikely that Dynamo will ever be able to trace through your code. Consider finding a workaround.
20+
21+
22+
23+
[Back to Registry](../index.md)

GBID directory/gb/gb0004.md

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# GB0004
2+
3+
## Graph-Break Type
4+
*Short name describing what triggered the graph break*
5+
Attempted super().__delattr__() on an object without mutation tracking
6+
7+
## Context
8+
*Values or code snippet captured at the break point*
9+
call_method {self} {name}
10+
11+
## Explanation
12+
*Why this specific graph break happened*
13+
Dynamo needs to track mutations on an object before `super().__delattr__` can be used on it. But the object ({self.objvar}) doesn't have attribute mutation tracking enabled.
14+
15+
## Hints
16+
*Suggestions for fixing or working around the break*
17+
- Ensure the object is tracked by Dynamo's side effect system.
18+
- This is likely to be a Dynamo bug. Please report an issue to PyTorch.
19+
20+
21+
22+
[Back to Registry](../index.md)

GBID directory/gb/gb0005.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# GB0005
2+
3+
## Graph-Break Type
4+
*Short name describing what triggered the graph break*
5+
Attempted to a str() method implemented in C/C++
6+
7+
## Context
8+
*Values or code snippet captured at the break point*
9+
*No context provided.*
10+
11+
## Explanation
12+
*Why this specific graph break happened*
13+
{type(arg.value)} has a C/C++ based str method. This is not supported.
14+
15+
## Hints
16+
*Suggestions for fixing or working around the break*
17+
- Write the str method in Python
18+
19+
20+
21+
[Back to Registry](../index.md)

GBID directory/gb/gb0006.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# GB0006
2+
3+
## Graph-Break Type
4+
*Short name describing what triggered the graph break*
5+
Attempted to call a super() attribute that is not a function or method
6+
7+
## Context
8+
*Values or code snippet captured at the break point*
9+
call_method {self} {name}
10+
11+
## Explanation
12+
*Why this specific graph break happened*
13+
Dynamo does not know how to trace the call `super().{name}()` because `super().{name}` is not a function or method attribute.
14+
15+
## Hints
16+
*Suggestions for fixing or working around the break*
17+
- Ensure the attribute accessed via `super()` is a standard method or function.
18+
19+
20+
21+
[Back to Registry](../index.md)

GBID directory/gb/gb0007.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# GB0007
2+
3+
## Graph-Break Type
4+
*Short name describing what triggered the graph break*
5+
Attempted to call function marked as skipped
6+
7+
## Context
8+
*Values or code snippet captured at the break point*
9+
module: {module_name}, qualname: {qualname}, skip reason: {reason}
10+
11+
## Explanation
12+
*Why this specific graph break happened*
13+
explanation
14+
15+
## Hints
16+
*Suggestions for fixing or working around the break*
17+
*No hints provided.*
18+
19+
20+
21+
[Back to Registry](../index.md)

GBID directory/gb/gb0008.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# GB0008
2+
3+
## Graph-Break Type
4+
*Short name describing what triggered the graph break*
5+
Attempted to inline function marked as skipped
6+
7+
## Context
8+
*Values or code snippet captured at the break point*
9+
qualname: {fn_qualname}, name: {func.get_name()}, filename: `{func.get_filename()}`, skip reason: {result.reason}
10+
11+
## Explanation
12+
*Why this specific graph break happened*
13+
Dynamo developers have intentionally marked that the function `{fn_qualname}` should not be traced.
14+
15+
## Hints
16+
*Suggestions for fixing or working around the break*
17+
*No hints provided.*
18+
19+
20+
21+
[Back to Registry](../index.md)

0 commit comments

Comments
 (0)