[pypy-commit] pypy guard-compatible: Don't use NULL, it doesn't always work here
arigo
pypy.commits at gmail.com
Fri Mar 23 11:04:55 EDT 2018
Author: Armin Rigo <arigo at tunes.org>
Branch: guard-compatible
Changeset: r94121:ff9206ab5e19
Date: 2018-03-23 16:02 +0100
http://bitbucket.org/pypy/pypy/changeset/ff9206ab5e19/
Log: Don't use NULL, it doesn't always work here
diff --git a/rpython/jit/backend/x86/vtune.py b/rpython/jit/backend/x86/vtune.py
--- a/rpython/jit/backend/x86/vtune.py
+++ b/rpython/jit/backend/x86/vtune.py
@@ -19,9 +19,9 @@
RPY_EXTERN void rpy_make_dlopen_strong(char *funcname, Signed addr, Signed size)
{
// make *really* sure that dlopen&Co are linked so that vtune is happy
- dlopen(NULL, 0);
- dlsym(NULL, NULL);
- dlclose(NULL);
+ dlopen((void *)0, 0);
+ dlsym((void *)0, (void *)0);
+ dlclose((void *)0);
}
RPY_EXTERN void rpy_vtune_register(char *funcname, Signed addr, Signed size)
More information about the pypy-commit
mailing list