Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #22410
Closed (moved) (moved)
Open
Issue created May 26, 2017 by Taylor Yu@catalyst

ensure that uint8_t is unsigned char

On a POSIX platform, uint8_t is required to exist, but not explicitly required to be identical to unsigned char. It's theoretically possible that a very unusual platform could have an extension integer type that it defines as uint8_t. Test for this at configure time.

This supports an effort to move toward using uint8_t as the "byte" type in preference to char (which is often a signed type and can cause bugs related to signed arithmetic).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking