ARCMWDT: continue RISC-V enablement #81481
Closed
Conversation
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
tagunil
force-pushed
the
mwdt-riscv-fixes
branch
3 times, most recently
from
590e134 to
b23ba27
Compare
tagunil
force-pushed
the
mwdt-riscv-fixes
branch
from
b23ba27 to
5ae581f
Compare
Raise minimal required version of ARC MWDT toolchain in preparation for RISC-V and Picolibc. Signed-off-by: Ilya Tagunov <[email protected]>
The new version of the ARC MWDT toolchain already supports C++20. Signed-off-by: Ilya Tagunov <[email protected]>
The SECTION_ macros have at least one significant issue, leading to symbols being put into sections with names like vectors() or text(). In practice it means that e.g. __start code appears at the end of the romable region instead of being at the beginning. Align these and other macro definitions with the ARC GCC ones, as the RISC-V side of ARC MWDT toolchain generates symbol names more like GCC, but the assembly language still uses ; for single line comments. Signed-off-by: Ilya Tagunov <[email protected]>
Newer versions of ARC MWDT toolchain provide built-in Picolibc in addition to the classic MW libc. For now it is available only for RISC-V processors, so keep it disabled for classic ARC ones. Signed-off-by: Ilya Tagunov <[email protected]>
The RISC-V variant of the classic MetaWare libc provides a thread-safe errno through TLS and uses it internally, so there is no point in having the hook. Just use the libc errno like we do for Picolibc. Signed-off-by: Ilya Tagunov <[email protected]>
ARC MWDT toolchain does not provide the GNU C++ Library, also known as libstdc++, so there is no way to run this test. Signed-off-by: Ilya Tagunov <[email protected]>
tagunil
force-pushed
the
mwdt-riscv-fixes
branch
from
5ae581f to
18dac03
Compare
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
|
This pull request has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this pull request will automatically be closed in 14 days. Note, that you can always re-open a closed pull request at any time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The current state of ARC MWDT toolchain support doesn't really allow building Zephyr for our ARC-V cores.