You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The reason will be displayed to describe this comment to others. Learn more.
@dbaston I strongly doubt this will ave any effect. -Werror=null-dereference has a number of false positives. I'd suggest you wrap the inclusion of exprtk.hpp with
The reason will be displayed to describe this comment to others. Learn more.
I will try that next. I can't figure out why the warning is even enabled in the first place, given that it's added as a system header which disables warnings on all other platforms that we test.
The reason will be displayed to describe this comment to others. Learn more.
given that it's added as a system header which disables warnings on all other platforms that we test.
you mean using bracketed include #include <exprtk.hpp> ? I don't think that disables gcc warning per se. In a number of situations where I didn't manage to shut off warnings, I create a thin include file with a #pragma GCC system_header before the actual include. Like https://github.com/OSGeo/gdal/blob/master/port/include_fast_float.h
36c0665
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dbaston I strongly doubt this will ave any effect. -Werror=null-dereference has a number of false positives. I'd suggest you wrap the inclusion of exprtk.hpp with
36c0665
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will try that next. I can't figure out why the warning is even enabled in the first place, given that it's added as a system header which disables warnings on all other platforms that we test.
https://github.com/OSGeo/gdal/pull/11209/files#diff-8efe41fec01001c2b54615fb45c5cd18865448b5be850a221afffe171c94e1fdR27
36c0665
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you mean using bracketed include
#include <exprtk.hpp>
? I don't think that disables gcc warning per se. In a number of situations where I didn't manage to shut off warnings, I create a thin include file with a#pragma GCC system_header
before the actual include. Like https://github.com/OSGeo/gdal/blob/master/port/include_fast_float.h36c0665
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean that that directory is flagged as a system directory in CMake:
It removed all of the exprtk warnings on other platforms, and every warning except this one on mingw.