Skip to content

Removed the Cortex-M asides from the Cortex-R52 module port - #784

Open
fdesbiens wants to merge 1 commit into
eclipse-threadx:devfrom
fdesbiens:rm-cortex-m-asides
Open

fdesbiens wants to merge 1 commit into
eclipse-threadx:devfrom
fdesbiens:rm-cortex-m-asides

Conversation

@fdesbiens

Copy link
Copy Markdown
Contributor

Four comments in the Cortex-R52 module port explained what the Cortex-M ports do instead of what this port does. A reader working on this port cannot act on any of it: the behaviour described belongs to a different architecture, and the surrounding comments already say what this port does and why.

The remaining text is unchanged. The abort vector still explains the three things it owes the fault handler and what omitting the first costs, the fault handler still explains why its two statements are ordered as they are, and the preamble still records that every GNU module port writes the entry-point words the same way.

The same two passages appear in the ThreadX Modules manual and are removed there in rtos-docs-asciidoc.

Comment-only. The port builds clean at 203 targets with zero warnings.

Four comments in the Cortex-R52 module port explained what the Cortex-M ports do
instead. A reader working on this port cannot act on any of it: the behaviour
described belongs to a different architecture, and the surrounding comments
already say what this port does and why.

The remaining text is unchanged. The abort vector still explains the three things
it owes the fault handler and what omitting the first costs, the fault handler
still explains why its two statements are ordered as they are, and the preamble
still says that every GNU module port writes the entry-point words the same way.

Comment-only. The port builds clean, 203 targets, zero warnings.

Assisted-by: Claude Code (Opus 5) <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant