| Revisión | 095ee62450e3dfdb7a3b94ba24b0c37190882314 (tree) |
|---|---|
| Tiempo | 2024-01-26 01:31:07 |
| Autor | Albert Mietus < albert AT mietus DOT nl > |
| Commiter | Albert Mietus < albert AT mietus DOT nl > |
small update in DocParts/ (local/hack docs)
CCastle/DocParts/Design/01.Architecture/01.AIGR_pipeline.rst (diff) CCastle/DocParts/Design/01.Architecture/99.todo.rst (diff)| @@ -54,7 +54,7 @@ | ||
| 54 | 54 | When implementing that (`Reader`) functionality is more convenient as after converting the :ref:`ATS into the AIGR |
| 55 | 55 | <AST-2-AIGR>` an “AIGR-analyser” is build. |
| 56 | 56 | |
| 57 | - | |
| 57 | +.. _Transformers: | |
| 58 | 58 | |
| 59 | 59 | Transformers |
| 60 | 60 | ============ |
| @@ -62,7 +62,10 @@ | ||
| 62 | 62 | All ‘`Transformers`’ receive and post (a “dialect” of) the`AIGR`, pushing it into a form that van be handled by the |
| 63 | 63 | backend to create an efficient binary. There can be many `Transformers`, and typically several of them are run in |
| 64 | 64 | sequence. Other sets of `Transformers` exclude each other. |
| 65 | -|BR| | |
| 65 | + | |
| 66 | + | |
| 67 | +A `Transformer` is often triggered by one of the :ref:`Rewriters` | |
| 68 | + | |
| 66 | 69 | We show two examples. |
| 67 | 70 | |
| 68 | 71 | .. uml:: AIGR_Transformers.puml |
| @@ -17,11 +17,6 @@ | ||
| 17 | 17 | Writers [ToDo] |
| 18 | 18 | ************** |
| 19 | 19 | |
| 20 | -.. _Transformers: | |
| 21 | - | |
| 22 | -Transformers [ToDo] | |
| 23 | -******************* | |
| 24 | - | |
| 25 | 20 | .. _Backends: |
| 26 | 21 | |
| 27 | 22 | Backends [ToDo] |
Fork