Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
K
kickc
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 263
    • Issues 263
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • camelot
  • kickc
  • Issues
  • #221

Closed
Open
Created Jul 16, 2019 by Jesper Balman Gravgaard@jespergravgaardOwner

Add better syntax for accessing bytes inside words/dwords.

The <w / >w syntax is OK for 16-bit words - but not very good for 32-bit words. When 24-bit words get introduced it will be even worse.

Currently to access byte 3 of a dword the following syntax is needed with spaces being important < > dw . This introduces a temporary word-variable holding the high-word of dw.

A better solution would be to introduce a better syntax for directly accessing bytes/words inside larger words/dwords.

Edited Jul 16, 2019 by Jesper Balman Gravgaard
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking