Repository navigation
doc: refine gnu/llvm known issues and link them from changelog - #83
Merged
Merged
Conversation
fanghuaqi
reviewed
Nov 5, 2026
| - `Known Issues <https://github.com/riscv-mcu/riscv-gnu-toolchain/issues/18>`_ | ||
| - GNU Known Issues: :ref:`Known Issues <toolchain_gnu_known_issues>` | ||
|
|
||
| - LLVM Known Issues: :ref:`Known Issues <toolchain_llvm_known_issues>` |
fanghuaqi
reviewed
Nov 5, 2026
|
|
||
| Access to Address 0 Is Compiled Into ``ebreak`` | ||
| ----------------------------------------------- | ||
| Access to Address 0 Is Compiled Into ``ebreak`` (Affects 2026.10/2025.10/2025.02) |
Member
There was a problem hiding this comment.
不用在标题里面写，在下面开个引用块，在里面写 影响哪些版本，在哪些版本里面修复
Member
|
@bigmagic123 我们这个版本不是新增了一些选项么，把新增的选项注明下是 2026.10增加进去的，然后也删掉了一些选项，删掉的选项也注明下是2026.10删掉的 |
Member
|
@bigmagic123 这个请更新下哈 |
- Drop the P1 bug mark from the known issue titles, they are known issues/limitations rather than bugs, keep the affected version annotations (2026.10/2025.10/2025.02) - Add references to the detailed description issues (#60 sscanf, #61 address 0 ebreak, #62 naked with varargs) - Remove the -Wa,-adhlns frame unwind issue entry, refer to the detailed description elsewhere instead - Point the changelog top note to the GNU/LLVM Known Issues doc sections, and mention issue #18 for more bug issues in both gnu and llvm known issues sections
- Move the affected/fixed version annotations of the known issues from the titles into note blocks below each entry - Describe the -maddibne/-mno-addibne option lifecycle: added in 2025.10, removed in 2026.10, replaced by -mautogen-xxlcz - Add a Nuclei Custom Options section to the llvm intro for the new -mautovec-rvv/-mautovec-dsp/-mautogen-xxlcz options (functionality not implemented yet, clang only accepts them without errors) - Link the libncrt 2026.10 known issues (_libncrt_202610_knownissues) from the changelog top note
Remove the -dev suffix from the sphinx version/release, and drop the under development warning banner from the overview introduction page, since the 2026.10 documentation is now released formally.
Replace the bare known issues link with a structured note, which points to the all-tools known issues index (nuclei-tool-guide#18) and the per-component known issues sections of GNU toolchain, LLVM toolchain and libncrt, following the same pattern as the toolchain changelog.
bigmagic123
force-pushed
the
nuclei/toolchain_doc
branch
from
November 9, 2026 09:02
4e1eec0 to
eda1b20
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.