Skip to content

Added ARMv7-A TX_THREAD offset checks - #800

Open
JeewoongKim wants to merge 1 commit into
eclipse-threadx:devfrom
JeewoongKim:fix/armv7a-gnu-offset-check
Open

JeewoongKim wants to merge 1 commit into
eclipse-threadx:devfrom
JeewoongKim:fix/armv7a-gnu-offset-check

Conversation

@JeewoongKim

@JeewoongKim JeewoongKim commented Oct 8, 2026 •

Copy link
Copy Markdown

Addresses the ARMv7-A portion of #577.

The ARMv7-A assembly uses hard-coded offsets to access TX_THREAD members.
This change adds compile-time checks to catch mismatches when the structure layout changes.

The checker is added to shared ARMv7-A source tree and propagated to all seven Cortex-A
GNU and AC6 ports using update.sh. The GNU CMake files are also updated to compile it.

I built all seven GNU ports A{5, 7, 8, 9, 12, 15, 17} and confirmed that an incorrect VFP offset
(148 instead of 144) causes a compilation failure. The AC6 ports were not built.

PR checklist

  • Updated function header with a short description and version number
  • Added test case for bug fix or new feature
  • Validated on real hardware

The ARMv7-A assembly uses hard-coded offsets to access TX_THREAD
members. Changes to the structure layout could break these accesses.

Added compile-time checks in the shared ARMv7-A source tree and
regenerated the GNU and AC6 port copies.

Built all seven GNU port and verified that an incorrect VFP offset
causes a compilation failure.

Assisted-by: ChatGPT (GPT-5.6 Sol)
@fdesbiens
fdesbiens self-requested a review October 16, 2026 13:35
@fdesbiens fdesbiens self-assigned this Oct 16, 2026

@fdesbiens fdesbiens left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @JeewoongKim. Thank you for this contribution. The assertions cover the hard-coded offsets I checked in the ARMv7-A assembly, and the reported GNU builds include a useful negative check. Could you resolve the commit’s Assisted-by trailer with the maintainer so it has the accepted format and an email address, and remove the AI-process paragraphs from the PR description? The stated AC6 build limitation is clear.

@JeewoongKim

Copy link
Copy Markdown
Author

Thanks for the review! I've removed the AI-process paragraphs from the PR description.

For the Assisted-by trailer, I found noreply@openai.com used for Codex attribution in OpenAI's repository,
but couldn't find an official email address for ChatGPT. Since I used ChatGPT rather than Codex,
would Assisted-by: ChatGPT (GPT-5.6 Sol) <noreply@openai.com> be acceptable, or is there a preferred address?

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.

2 participants