-
-
Notifications
You must be signed in to change notification settings - Fork 114
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fudge code to get rid of warnings from GCC
GCC is generating some spurious warnings: * The OSMObject::user() functions returns a pointer outside the OSMObject. That's okay, because we know we put the data there, but GCC thinks this is fishy. We can not disable the stringop-overread warning inside the library, because it is only produced in the users code. But the magic [[gnu::noipa]]attribute stops GCC from looking through the user() call and the warning doesn't happen. Because older GCCs and other compilers don't understand the attribute, we have to check for the compiler version. * The Tag::after_null() call similarly triggers an array-bounds warning, which the changes code doesn't for some reason.
- Loading branch information
Showing
4 changed files
with
13 additions
and
13 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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