skills.rest
qualcomm
qualcommOFFICIAL
Explore all skills by this author →
WebsiteGitHub

arm64-baseline-porting

Apply ARM64 architectural constraints during x64 code porting.

2|1|Updated Mar 26, 2026
Search Tags:#fallback#architectural constraints#arm64#porting#windows arm64
One-click install
npx skills add https://github.com/qualcomm/EasyWoS --skill arm64-baseline-porting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: arm64-baseline-porting
Source: https://github.com/qualcomm/EasyWoS/tree/main/agent/skills/arm64-baseline-porting
Command: npx skills add https://github.com/qualcomm/EasyWoS --skill arm64-baseline-porting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill serves as a fallback for ARM64 porting when specific specifications are not applicable, ensuring that the ported code adheres to fundamental architectural constraints.

Core Features & Use Cases

  • Fallback for ARM64 Porting: Applies mandatory architectural constraints for all ARM64 migrations.
  • Architectural Constraints: Includes Windows ARM64 ABI, memory ordering, NEON width limits, ABI shims, and intrinsic hygiene.
  • Use Case: When migrating x64 code to ARM64 with no specific spec matched, use this Skill to ensure correctness regardless of code pattern.

Quick Start

Run the skill with the command: /ospx:apply

Frequently Asked Questions about arm64-baseline-porting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure ARM64 porting correctness when migrating x64 code without specific specifications?▼

To ensure ARM64 porting correctness without specific specs, apply mandatory architectural constraints for Windows ARM64 ABI, weak memory ordering, NEON limits, ARM64EC shims, and intrinsic safety. This fallback approach guarantees fundamental architectural compliance regardless of code pattern.

What architectural constraints must be applied during Windows ARM64 porting?▼

Windows ARM64 porting requires applying architectural constraints for the Windows ARM64 ABI, weak memory ordering, NEON width limits, ARM64EC shims, and intrinsic hygiene to maintain architectural invariants and ensure code correctness.

When do I need to use fallback rules for ARM64 code migration?▼

Fallback rules for ARM64 code migration are needed when specific porting specifications are absent or when freeform ARM64 output is required, ensuring ported code adheres to fundamental architectural constraints.

Does ARM64 porting require specific handling for weak memory ordering and NEON limits?▼

Yes, ARM64 porting requires specific handling for weak memory ordering and NEON width limits. Applying these mandatory architectural constraints ensures compliance with ARM64 architectural invariants during code migration.

What is the best way to handle ARM64EC shims and intrinsic safety during porting?▼

The best way to handle ARM64EC shims and intrinsic safety during porting is to apply mandatory architectural constraints that enforce ARM64 architectural invariants, ensuring correct fallback behavior when specific specifications are not applicable.

Related Skills

Explore More Software Engineering Skills→
qualcommqualcomm
2

asm-x64-to-arm64

Convert x64 assembly instructions to AArch64 using translation rules and syntax mappings.

Official
Advanced
qualcommqualcomm
2

intrinsics-x64-to-arm64

Migrate x86/x64 SIMD code to ARM64 NEON with intrinsic mappings.

Official
Advanced
ovachieverovachiever
52

deepspeed

Guide DeepSpeed distributed training with ZeRO, pipeline parallelism, and mixed precision.

Community
Advanced
LLaammTTeerrLLaammTTeerr

preparing-tests

Automate creation and verification of test data, validators, and checkers for competitive programming problems.

Community
Advanced