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

Fixed all clang -Wsigned-enum-bitfield warnings #2833

Closed
wants to merge 1 commit into from

Conversation

seanm
Copy link
Contributor

@seanm seanm commented Mar 24, 2022

Made enums involved in bitfields unsigned.

Used unsigned char specifically because gcc before 9.3 seems to have a bug where it warns about bitfields not being big enough to hold the enum, even though they are.

Made enums involved in bitfields unsigned.

Used unsigned char specifically because gcc before 9.3 seems to have a bug where it warns about bitfields not being big enough to hold the enum, even though they are.
@seanm
Copy link
Contributor Author

seanm commented Mar 24, 2022

So I'm just headed on vacation, but when back I'll take another stab at making the old gcc happy...

@vitaut
Copy link
Contributor

vitaut commented Apr 6, 2022

Closing for now to reduce noise but feel free to reopen once it's ready for review.

@vitaut vitaut closed this Apr 6, 2022
@seanm
Copy link
Contributor Author

seanm commented May 5, 2022

@vitaut I don't think I have permission to reopen this issue, but I have an updated commit. Can you reopen this please?

@vitaut
Copy link
Contributor

vitaut commented May 5, 2022

Unfortunately I cannot reopen it either because the branch was force-pushed so you'll have to create a new PR.

@seanm
Copy link
Contributor Author

seanm commented May 5, 2022

I pushed my updated commit, which I thought would automatically reopen this PR, but I guess that's not how github works? Must one first reopen a PR before updating it?

Anyway, new PR coming...

@seanm
Copy link
Contributor Author

seanm commented May 5, 2022

#2882

@vitaut
Copy link
Contributor

vitaut commented May 5, 2022

Must one first reopen a PR before updating it?

I think so. GitHub is weird in this respect.

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

Successfully merging this pull request may close these issues.

2 participants