Skip to content

Commit f924dfe

Browse files
ilg-ulilg-ul
committed
website: re-generate blog
1 parent ef2500a commit f924dfe

23 files changed

+31
-31
lines changed

‎website/blog/2019-07-31-riscv-none-embed-gcc-v8-2-0-3-1-released.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The binary files are available from <a href={ frontMatter.download_url }>GitHub
3030

3131
## Install
3232

33-
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
33+
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
3434
various platforms are presented in the project [README](https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack).
3535

3636
## Compliance

‎website/blog/2019-11-01-riscv-none-embed-gcc-v8-3-0-1-1-released.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ The binary files are available from <a href={ frontMatter.download_url }>GitHub
3030

3131
## Install
3232

33-
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
33+
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
3434
various platforms are presented in the project [README](https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack).
3535

3636
## Compliance
@@ -112,7 +112,7 @@ library was mostly empty; the script was fixed and now the library has the
112112
expected content.
113113
- [[#4]](https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack/issues/4)
114114
Due to a bug in the build scripts, the Windows binaries included two
115-
copies of the `docs` folder, one in root and one in the `share` folder;
115+
copies of the `docs` folder, one in root and one in the `share` folder;
116116
the script was fixed and now there is only one copy in `share/docs`.
117117

118118
## Improvements

‎website/blog/2020-07-04-riscv-none-embed-gcc-v8-3-0-1-2-released.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ The binary files are available from <a href={ frontMatter.download_url }>GitHub
3939

4040
## Install
4141

42-
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
42+
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
4343
various platforms are presented in the project [README](https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack).
4444

4545
## Compliance

‎website/blog/2020-10-10-riscv-none-embed-gcc-v8-3-0-2-1-released.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ The binary files are available from <a href={ frontMatter.download_url }>GitHub
4242

4343
## Install
4444

45-
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
45+
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
4646
various platforms are presented in the project [README](https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack).
4747

4848
## Compliance
@@ -221,7 +221,7 @@ TUI is not available on Windows
221221
the bug was fixed in binutils 2.33.1, and the fix was included in the
222222
next **8.3.0-2.2** release;
223223
- the archive size got too big for the Windows 32-bit node to handle, and
224-
`xpm install` fails with _RangeError: Array buffer allocation failed_.
224+
`xpm install` fails with _RangeError: Array buffer allocation failed_.
225225

226226
## Documentation
227227

‎website/blog/2020-10-13-riscv-none-embed-gcc-v8-3-0-2-2-released.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The binary files are available from <a href={ frontMatter.download_url }>GitHub
4545

4646
## Install
4747

48-
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
48+
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
4949
various platforms are presented in the project [README](https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack).
5050

5151
## Compliance
@@ -236,7 +236,7 @@ and LENGTH and ORIGIN are now recognised as expected.
236236
it is a known problem, caused when trying to create the cache
237237
folder (`$HOME/.cache/gdb` or `$HOME/Library/Caches/gdb`);
238238
- the archive size got too big for the Windows 32-bit node to handle, and
239-
`xpm install` fails with _RangeError: Array buffer allocation failed_.
239+
`xpm install` fails with _RangeError: Array buffer allocation failed_.
240240

241241
## Documentation
242242

‎website/blog/2020-10-25-riscv-none-embed-gcc-v8-3-0-2-3-released.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The binary files are available from <a href={ frontMatter.download_url }>GitHub
4545

4646
## Install
4747

48-
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
48+
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
4949
various platforms are presented in the project [README](https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack).
5050

5151
## Compliance
@@ -191,7 +191,7 @@ TUI is not available on Windows
191191
it is a known problem, caused when trying to create the cache
192192
folder (`$HOME/.cache/gdb` or `$HOME/Library/Caches/gdb`);
193193
- the archive size got too big for the Windows 32-bit node to handle, and
194-
`xpm install` fails with _RangeError: Array buffer allocation failed_.
194+
`xpm install` fails with _RangeError: Array buffer allocation failed_.
195195

196196
## Documentation
197197

‎website/blog/2021-01-05-riscv-none-embed-gcc-v10-1-0-1-1-released.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The binary files are available from <a href={ frontMatter.download_url }>GitHub
4545

4646
## Install
4747

48-
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
48+
The full details of installing the **xPack GNU RISC-V Embedded GCC** on
4949
various platforms are presented in the project [README](https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack).
5050

5151
## Compliance
@@ -185,7 +185,7 @@ TUI is not available on Windows
185185
(~70K), the compiler sources became too large and it was not possible to build the Arm 32-bit image
186186
([#229](https://github.com/riscv/riscv-gcc/issues/229))
187187
- the archive size got too big for the Windows 32-bit node to handle, and
188-
`xpm install` may fail with _RangeError: Array buffer allocation failed_;
188+
`xpm install` may fail with _RangeError: Array buffer allocation failed_;
189189
the 64-bit systems are not affected.
190190

191191
## Documentation

‎website/blog/2021-11-04-riscv-none-embed-gcc-v10-1-0-1-2-released.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ The binary files are available from <a href={ frontMatter.download_url }>GitHub
6666

6767
## Install
6868

69-
The full details of installing the **xPack GNU RISC-V Embedded GCC** on various platforms
69+
The full details of installing the **xPack GNU RISC-V Embedded GCC** on various platforms
7070
are presented in the project [README](https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack).
7171

7272
## Compliance
@@ -155,7 +155,7 @@ TUI is not available on Windows
155155
(~70K), the compiler sources became too large and it was not possible to build the Arm 32-bit image
156156
([#229](https://github.com/riscv/riscv-gcc/issues/229))
157157
- the archive size got too big for the Windows 32-bit node to handle, and
158-
`xpm install` may fail with _RangeError: Array buffer allocation failed_;
158+
`xpm install` may fail with _RangeError: Array buffer allocation failed_;
159159
the 64-bit systems are not affected.
160160

161161
## Documentation

‎website/blog/2021-11-06-riscv-none-embed-gcc-v10-2-0-1-1-released.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ The binary files are available from <a href={ frontMatter.download_url }>GitHub
6666

6767
## Install
6868

69-
The full details of installing the **xPack GNU RISC-V Embedded GCC** on various platforms
69+
The full details of installing the **xPack GNU RISC-V Embedded GCC** on various platforms
7070
are presented in the project [README](https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack).
7171

7272
## Compliance
@@ -155,7 +155,7 @@ TUI is not available on Windows
155155
(~70K), the compiler sources became too large and it was not possible to build the Arm 32-bit image
156156
([#229](https://github.com/riscv/riscv-gcc/issues/229))
157157
- the archive size got too big for the Windows 32-bit node to handle, and
158-
`xpm install` may fail with _RangeError: Array buffer allocation failed_;
158+
`xpm install` may fail with _RangeError: Array buffer allocation failed_;
159159
the 64-bit systems are not affected.
160160

161161
## Documentation

‎website/blog/2021-11-11-riscv-none-embed-gcc-v10-2-0-1-2-released.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ The binary files are available from <a href={ frontMatter.download_url }>GitHub
6666

6767
## Install
6868

69-
The full details of installing the **xPack GNU RISC-V Embedded GCC** on various platforms
69+
The full details of installing the **xPack GNU RISC-V Embedded GCC** on various platforms
7070
are presented in the project [README](https://github.com/xpack-dev-tools/riscv-none-embed-gcc-xpack).
7171

7272
## Compliance
@@ -298,7 +298,7 @@ TUI is not available on Windows
298298
(~70K), the compiler sources became too large and it was not possible to build the Arm 32-bit image
299299
([#229](https://github.com/riscv/riscv-gcc/issues/229))
300300
- the archive size got too big for the Windows 32-bit node to handle, and
301-
`xpm install` may fail with _RangeError: Array buffer allocation failed_;
301+
`xpm install` may fail with _RangeError: Array buffer allocation failed_;
302302
the 64-bit systems are not affected.
303303

304304
## Documentation

0 commit comments

Comments
 (0)