public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros
@ 2022-08-01 11:52 Martin Liska
0 siblings, 0 replies; 11+ messages in thread
From: Martin Liska @ 2022-08-01 11:52 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:fb371bb20c51d04cec2fdd255a10a4ce746697eb
commit fb371bb20c51d04cec2fdd255a10a4ce746697eb
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 4e5e918ea86..cc999d3406f 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]
@@ -3873,13 +3873,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)).
@@ -3897,7 +3897,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 21cff47607a..5477c13f027 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\
@@ -4259,13 +4259,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\
@@ -4281,7 +4281,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] 11+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros
@ 2022-08-01 4:03 Martin Liska
0 siblings, 0 replies; 11+ messages in thread
From: Martin Liska @ 2022-08-01 4:03 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:cf6dbcffdb918fc31e7c14d2c7020ec2d3fe767f
commit cf6dbcffdb918fc31e7c14d2c7020ec2d3fe767f
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
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 4e5e918ea86..cc999d3406f 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]
@@ -3873,13 +3873,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)).
@@ -3897,7 +3897,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 21cff47607a..5477c13f027 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\
@@ -4259,13 +4259,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\
@@ -4281,7 +4281,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] 11+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros
@ 2022-07-28 13:19 Martin Liska
0 siblings, 0 replies; 11+ messages in thread
From: Martin Liska @ 2022-07-28 13:19 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:0ca3928056bd3eb407ac89a54bf45aa6000cda2e
commit 0ca3928056bd3eb407ac89a54bf45aa6000cda2e
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
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 4e5e918ea86..cc999d3406f 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]
@@ -3873,13 +3873,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)).
@@ -3897,7 +3897,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 21cff47607a..5477c13f027 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\
@@ -4259,13 +4259,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\
@@ -4281,7 +4281,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] 11+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros
@ 2022-07-28 12:39 Martin Liska
0 siblings, 0 replies; 11+ messages in thread
From: Martin Liska @ 2022-07-28 12:39 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:674b084d77a658e017508afdc00733f899800deb
commit 674b084d77a658e017508afdc00733f899800deb
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
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 4e5e918ea86..cc999d3406f 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]
@@ -3873,13 +3873,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)).
@@ -3897,7 +3897,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 21cff47607a..5477c13f027 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\
@@ -4259,13 +4259,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\
@@ -4281,7 +4281,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] 11+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros
@ 2022-07-28 12:22 Martin Liska
0 siblings, 0 replies; 11+ messages in thread
From: Martin Liska @ 2022-07-28 12:22 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:0852ed21a257d93a5b9d83752a82f3d00d4d2827
commit 0852ed21a257d93a5b9d83752a82f3d00d4d2827
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
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 4e5e918ea86..cc999d3406f 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]
@@ -3873,13 +3873,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)).
@@ -3897,7 +3897,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 21cff47607a..5477c13f027 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\
@@ -4259,13 +4259,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\
@@ -4281,7 +4281,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] 11+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros
@ 2022-07-27 14:48 Martin Liska
0 siblings, 0 replies; 11+ messages in thread
From: Martin Liska @ 2022-07-27 14:48 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:28a4dcac4495dcea314230ab7d772ccca118ac29
commit 28a4dcac4495dcea314230ab7d772ccca118ac29
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
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 4e5e918ea86..cc999d3406f 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]
@@ -3873,13 +3873,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)).
@@ -3897,7 +3897,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 21cff47607a..5477c13f027 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\
@@ -4259,13 +4259,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\
@@ -4281,7 +4281,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] 11+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros
@ 2022-07-27 12:18 Martin Liska
0 siblings, 0 replies; 11+ messages in thread
From: Martin Liska @ 2022-07-27 12:18 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:98d320c32d1d27cb67d0b3b93a305cf81c34f1da
commit 98d320c32d1d27cb67d0b3b93a305cf81c34f1da
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
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 4e5e918ea86..cc999d3406f 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]
@@ -3873,13 +3873,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)).
@@ -3897,7 +3897,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 21cff47607a..5477c13f027 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\
@@ -4259,13 +4259,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\
@@ -4281,7 +4281,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] 11+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros
@ 2022-07-26 12:50 Martin Liska
0 siblings, 0 replies; 11+ messages in thread
From: Martin Liska @ 2022-07-26 12:50 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:540e4c0ac85d9afdcadb78d06f5ff7aee002c713
commit 540e4c0ac85d9afdcadb78d06f5ff7aee002c713
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
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 4e5e918ea86..cc999d3406f 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]
@@ -3873,13 +3873,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)).
@@ -3897,7 +3897,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 21cff47607a..5477c13f027 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\
@@ -4259,13 +4259,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\
@@ -4281,7 +4281,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] 11+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros
@ 2022-07-26 12:44 Martin Liska
0 siblings, 0 replies; 11+ messages in thread
From: Martin Liska @ 2022-07-26 12:44 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:46ee39c9592726eb3aa15bb41f7c374c598b56c7
commit 46ee39c9592726eb3aa15bb41f7c374c598b56c7
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
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 4e5e918ea86..cc999d3406f 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]
@@ -3873,13 +3873,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)).
@@ -3897,7 +3897,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 21cff47607a..5477c13f027 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\
@@ -4259,13 +4259,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\
@@ -4281,7 +4281,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] 11+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros
@ 2022-07-26 12:43 Martin Liska
0 siblings, 0 replies; 11+ messages in thread
From: Martin Liska @ 2022-07-26 12:43 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:13dbdcc27ac97f5bddc0a49fb5047f7997540d48
commit 13dbdcc27ac97f5bddc0a49fb5047f7997540d48
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
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 4e5e918ea86..cc999d3406f 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]
@@ -3873,13 +3873,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)).
@@ -3897,7 +3897,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 21cff47607a..5477c13f027 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\
@@ -4259,13 +4259,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\
@@ -4281,7 +4281,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] 11+ messages in thread
* [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros
@ 2022-07-26 12:14 Martin Liska
0 siblings, 0 replies; 11+ messages in thread
From: Martin Liska @ 2022-07-26 12:14 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:ef1024b5fa695db0936529807cd91e6f68c07a99
commit ef1024b5fa695db0936529807cd91e6f68c07a99
Author: Martin Liska <mliska@suse.cz>
Date: Tue Jul 26 14:14:19 2022 +0200
sphinx: use proper lexers for target macros
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 4e5e918ea86..cc999d3406f 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]
@@ -3873,13 +3873,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)).
@@ -3897,7 +3897,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 21cff47607a..5477c13f027 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\
@@ -4259,13 +4259,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\
@@ -4281,7 +4281,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] 11+ messages in thread
end of thread, other threads:[~2022-08-01 11:52 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-08-01 11:52 [gcc(refs/users/marxin/heads/sphinx-v7)] sphinx: use proper lexers for target macros Martin Liska
-- strict thread matches above, loose matches on Subject: below --
2022-08-01 4:03 Martin Liska
2022-07-28 13:19 Martin Liska
2022-07-28 12:39 Martin Liska
2022-07-28 12:22 Martin Liska
2022-07-27 14:48 Martin Liska
2022-07-27 12:18 Martin Liska
2022-07-26 12:50 Martin Liska
2022-07-26 12:44 Martin Liska
2022-07-26 12:43 Martin Liska
2022-07-26 12:14 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).