Add _Bool support to TAU_OVERLOAD_PRINTER for GCC compatibility#60
Merged
Conversation
GCC requires an explicit association for _Bool in C11 _Generic selections. Without this, assertions on boolean values fail to compile with: "error: '_Generic' selector of type '_Bool' is not compatible with any association" This change maps _Bool to the "%d" format specifier.
jasmcaus
approved these changes
Jan 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes a compilation error encountered when using GCC (specifically aarch64-linux-gnu-gcc in my case) to assert boolean values.
When using CHECK_EQ (or other macros) on a function returning a bool or a boolean literal, GCC fails to select a matching type in the _Generic association within TAU_OVERLOAD_PRINTER. This results in the following error:
This happens because _Bool is a distinct type in C11, and without an explicit entry in the generic selection, it doesn't fall back to int or unsigned int automatically in this context.