Skip to content

Specify signed char instead of char #423

Open
@b04505009

Description

I got this compilation warning when compiling for aarch64

yuv_io.c: In function 'read_frame_header':
yuv_io.c:210:21: warning: comparison is always false due to limited range of data type [-Wtype-limits]
  210 |       if (buffer[i] == EOF) return 0;
      |                     ^~

Since char is unsigned on arm, should we specify signed char in general?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions