Skip to content

Conversation

@badochov
Copy link

@badochov badochov commented Oct 17, 2024

JIRA: RTOS-909

Description

Motivation and Context

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (refactoring, style fixes, git/CI config, submodule management, no code logic changes)

How Has This Been Tested?

  • Already covered by automatic testing.
  • New test added: (add PR link here).
  • Tested by hand on: (list targets here).

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing linter checks and tests passed.
  • My changes generate no new compilation warnings for any of the targets.

Special treatment

  • This PR needs additional PRs to work (list the PRs, preferably in merge-order).
  • I will merge this PR by myself when appropriate.

@badochov badochov requested a review from nalajcie October 17, 2024 16:17
@github-actions
Copy link

Unit Test Results

7 741 tests  ±0   7 026 ✅ ±0   41m 36s ⏱️ + 1m 52s
  461 suites ±0     715 💤 ±0 
    1 files   ±0       0 ❌ ±0 

Results for commit 5d44e55. ± Comparison against base commit 6cab908.

@nalajcie
Copy link
Member

why exactly is this needed?

@badochov
Copy link
Author

why exactly is this needed?

This adds the GNU_STACK_NOTE section to ASM files as you asked.

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.

3 participants