public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-07 14:07 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-07 14:07 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:49588ef344d991d0cf384d2b22030b6201398128
commit 49588ef344d991d0cf384d2b22030b6201398128
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-08 14:53 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-08 14:53 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:2bdd083c9afc3e1b0b316c5ed01d19ce0924d02c
commit 2bdd083c9afc3e1b0b316c5ed01d19ce0924d02c
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-08 14:43 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-08 14:43 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:0aadfb3dbedee2215077ffeee448001756e3be8b
commit 0aadfb3dbedee2215077ffeee448001756e3be8b
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-08 14:36 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-08 14:36 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:6aa5e916a4677c53bd6ec943307976d0142f9727
commit 6aa5e916a4677c53bd6ec943307976d0142f9727
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-08 14:35 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-08 14:35 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:c0597ad6ea1d53fb242fa83db46cd9862546e44f
commit c0597ad6ea1d53fb242fa83db46cd9862546e44f
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-08 12:06 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-08 12:06 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:276ef5fcd837db0296bb0af50503180dbc7a7ed2
commit 276ef5fcd837db0296bb0af50503180dbc7a7ed2
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-08 11:39 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-08 11:39 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:5800ccf9f03c6bc0ee971686fde3cd10b2a8d867
commit 5800ccf9f03c6bc0ee971686fde3cd10b2a8d867
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-08 10:21 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-08 10:21 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:b116fdf8ce55474bda762d1eeb57b45a4f67f5df
commit b116fdf8ce55474bda762d1eeb57b45a4f67f5df
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-07 14:34 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-07 14:34 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:addf5bcec7d76822b5f69faaddb86a515fb31bd4
commit addf5bcec7d76822b5f69faaddb86a515fb31bd4
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-07 14:19 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-07 14:19 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:4fee0acd738a76e0140e571a3102003057695522
commit 4fee0acd738a76e0140e571a3102003057695522
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-07 14:09 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-07 14:09 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:d8df14120cef04583af64e22fb30abb7c66123cb
commit d8df14120cef04583af64e22fb30abb7c66123cb
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-07 14:08 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-07 14:08 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:ac6522ad5583b78819815d700b64ed87e5ea22d3
commit ac6522ad5583b78819815d700b64ed87e5ea22d3
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-07 13:20 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-07 13:20 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:ce4c5d1023f9b41e0b5cd4eda1818c1f6f8dc9f7
commit ce4c5d1023f9b41e0b5cd4eda1818c1f6f8dc9f7
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-07 13:01 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-07 13:01 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:f9fc2b911dfde3bdc563da6bef16bf4dc6394f83
commit f9fc2b911dfde3bdc563da6bef16bf4dc6394f83
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros
@ 2022-11-07 12:38 Martin Liska
0 siblings, 0 replies; 15+ messages in thread
From: Martin Liska @ 2022-11-07 12:38 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:9dd8af692c81597ecbaa6f084669b861cc1dac22
commit 9dd8af692c81597ecbaa6f084669b861cc1dac22
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
gcc/ChangeLog:
* target.def: Use proper lexers for target macros.
* doc/gccint/target-macros/tm.rst.in: Re-generate.
Diff:
---
gcc/doc/gccint/target-macros/tm.rst.in | 12 ++++++------
gcc/target.def | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/gcc/doc/gccint/target-macros/tm.rst.in b/gcc/doc/gccint/target-macros/tm.rst.in
index 17fc9e1b0aa..44f3a3b2222 100644
--- a/gcc/doc/gccint/target-macros/tm.rst.in
+++ b/gcc/doc/gccint/target-macros/tm.rst.in
@@ -1332,7 +1332,7 @@
Given below example:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4]
add r4, r4, r10
@@ -1349,7 +1349,7 @@
this scheduling fusion pass works. This hook calculates priority for each
instruction based on its fustion type, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r10, [r1, 4] ; fusion_pri=99, pri=96
add r4, r4, r10 ; fusion_pri=100, pri=100
@@ -1364,7 +1364,7 @@
to the priorities. As a result, instructions of same fusion type will be
pushed together in instruction flow, like:
- .. code-block:: c++
+ .. code-block:: gas
ldr r11, [r1, 0]
ldr r10, [r1, 4]
@@ -3876,13 +3876,13 @@
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging
info engine will invoke it on insns of the form
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec [...] UNSPEC_INDEX))
and
- .. code-block:: c++
+ .. code-block::
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).
@@ -3900,7 +3900,7 @@
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such
that the value of the indeterminate is:
- .. code-block:: c++
+ .. code-block::
value_of(R) / factor - offset
diff --git a/gcc/target.def b/gcc/target.def
index 7751b7fe7b1..aed1c1d3e22 100644
--- a/gcc/target.def
+++ b/gcc/target.def
@@ -1552,7 +1552,7 @@ instructions.\n\
\n\
Given below example:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4]\n\
add r4, r4, r10\n\
@@ -1569,7 +1569,7 @@ loads are actually next to each other in instruction flow. That's where\n\
this scheduling fusion pass works. This hook calculates priority for each\n\
instruction based on its fustion type, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r10, [r1, 4] ; fusion_pri=99, pri=96\n\
add r4, r4, r10 ; fusion_pri=100, pri=100\n\
@@ -1584,7 +1584,7 @@ Scheduling fusion pass then sorts all ready to issue instructions according\n\
to the priorities. As a result, instructions of same fusion type will be\n\
pushed together in instruction flow, like:\n\
\n\
-.. code-block:: c++\n\
+.. code-block:: gas\n\
\n\
ldr r11, [r1, 0]\n\
ldr r10, [r1, 4]\n\
@@ -4262,13 +4262,13 @@ DEFHOOK
contain UNSPECs or UNSPEC_VOLATILEs. The DWARF 2 call frame debugging\n\
info engine will invoke it on insns of the form\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec [...] UNSPEC_INDEX))\n\
\n\
and\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
(set (reg) (unspec_volatile [...] UNSPECV_INDEX)).\n\
\n\
@@ -4284,7 +4284,7 @@ expression, with :samp:`{i}` counting from 1. Return the number of a DWARF\n\
register :samp:`{R}` and set :samp:`*{factor}` and :samp:`*{offset}` such\n\
that the value of the indeterminate is:\n\
\n\
-.. code-block:: c++\n\
+.. code-block::\n\
\n\
value_of(R) / factor - offset\n\
\n\
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2022-11-08 14:53 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-07 14:07 [gcc(refs/users/marxin/heads/sphinx-final)] sphinx: use proper lexers for target macros Martin Liska
-- strict thread matches above, loose matches on Subject: below --
2022-11-08 14:53 Martin Liska
2022-11-08 14:43 Martin Liska
2022-11-08 14:36 Martin Liska
2022-11-08 14:35 Martin Liska
2022-11-08 12:06 Martin Liska
2022-11-08 11:39 Martin Liska
2022-11-08 10:21 Martin Liska
2022-11-07 14:34 Martin Liska
2022-11-07 14:19 Martin Liska
2022-11-07 14:09 Martin Liska
2022-11-07 14:08 Martin Liska
2022-11-07 13:20 Martin Liska
2022-11-07 13:01 Martin Liska
2022-11-07 12:38 Martin Liska
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).