-
Notifications
You must be signed in to change notification settings - Fork 608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
warning unknown attribute 'no_sanitize' in hb.hh with xlc16/xlclang #1852
Comments
Small potential patch for the issue
|
Thanks. Given that the compiler involved does seem to impersonate clang, and that this is just a warning, any reason we should fix it instead of just ignoring? |
Reason is that we want to achieve building the codebase in OpenJDK (including harfbuzz) with "warnings as errors" (we do this already on most other platforms). |
I'm glad to hear that the code compiles almost warning-free. Fixed. Thanks. |
When building the currently included harfbuzz in OpenJDK on AIX with the latest xlc16/xlclang compiler, we run into this warning :
In file included from /jdk/src/java.desktop/share/native/libfontmanager/harfbuzz/hb-aat-layout.cc:37:
In file included from /jdk/src/java.desktop/share/native/libfontmanager/harfbuzz/hb-aat-layout-kerx-table.hh:31:
/jdk/src/java.desktop/share/native/libfontmanager/harfbuzz/hb-kern.hh:46:3: warning: unknown attribute 'no_sanitize' ignored [-Wunknown-attributes]
HB_NO_SANITIZE_SIGNED_INTEGER_OVERFLOW
^
/jdk/src/java.desktop/share/native/libfontmanager/harfbuzz/hb.hh:363:63: note: expanded from macro 'HB_NO_SANITIZE_SIGNED_INTEGER_OVERFLOW'
#define HB_NO_SANITIZE_SIGNED_INTEGER_OVERFLOW attribute((no_sanitize("signed-integer-overflow")))
Coding : in hb.hh :
#if defined(clang)
/* Disable certain sanitizer errors. /
/ #1247 */
#define HB_NO_SANITIZE_SIGNED_INTEGER_OVERFLOW attribute((no_sanitize("signed-integer-overflow")))
#else
#define HB_NO_SANITIZE_SIGNED_INTEGER_OVERFLOW
#endif
I think the “#else” - case of the macro should be used when building with AIX xlc16/xlclang .
The text was updated successfully, but these errors were encountered: