Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Portability of bit fields #9

Open
giomba opened this issue Jan 12, 2024 · 0 comments
Open

Portability of bit fields #9

giomba opened this issue Jan 12, 2024 · 0 comments

Comments

@giomba
Copy link
Collaborator

giomba commented Jan 12, 2024

Because of portability reasons, I've always avoided bit fields, and done bit masking operations by hand.

Sort of religious thought. What does even portability mean? If the compiler's implementation is coherent with itself (as it should be), does this problem even arise? I don't think we are going to link together objects produced by different compilers, or mix binaries of different architectures. We don't even need low level access to hardware registers, this is "high level" software.

Anyhow, some thoughts need to be done about:

  • consequences of using bit fields in src/fdc.c
  • consequences of accessing raw video memory in src/video.c
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

No branches or pull requests

1 participant