Skip to content

Conversation

@snickerbockers
Copy link
Contributor

at the cleanup label, it checks if chd.file != NULL, but if filename
or header was NULL then chd will be uninitialized

i saw this as a gcc warning while building libchdr. IDK if it is
causing any problems but it is definitely something that should be fixed.

at the cleanup label, it checks if chd.file != NULL, but if filename
or header was NULL then chd will be uninitialized

i saw this as a gcc warning while building libchdr.  IDK if it is
causing any problems but it is definitely something that should be fixed.
@hrydgard
Copy link
Contributor

hrydgard commented Jun 8, 2025

There are more warnings than this when building with a new compiler, would be nice with some cleaner output.

@rtissera
Copy link
Owner

rtissera commented Jun 8, 2025

@hrydgard Agreed, we need to clean up and accomodate newer Clang / GCC while keeping compatibility with older GCC / exotic old toolchains

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.

3 participants