GTiff: Avoid value-initialization of vector of forward declared class#14743
Merged
Conversation
Contributor
Author
|
Oh, this apparently needs another approach:
|
Addresses "invalid application of 'sizeof' to an incomplete type 'GTiffJPEGOverviewDS'" compiler error on macOS 12 and earlier (with AppleClang 13 and earlier).
04e3c5a to
3249338
Compare
Contributor
Author
|
Now I believe it should be ok. |
rouault
approved these changes
Jun 8, 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
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.
What does this PR do?
Trigger default-initialisation instead of value-initialisation of vector of forward declared class (in frmts/gtiff/gtiffdataset.h).
Addresses "invalid application of 'sizeof' to an incomplete type 'GTiffJPEGOverviewDS'" compiler error on macOS 12 and earlier (with AppleClang 13 and earlier):
This wasn't an issue on macOS 13 and newer, I can't test this fix on the failing platform but it compiles fine on macOS 26. I noticed this failure on MacPorts' build logs.
What are related issues/pull requests?
AI tool usage
Tasklist
Environment
Provide environment details, if relevant: