It has been reported that the glib-supplied tapset files {32,64}-gobject.stp are near-duplicates of one another, specifically they contain identical global gtypes If an end-user script causes both tapset files to be processed, this results in semantic error: conflicting global variables: identifier 'gtypes' at /usr/share/systemtap/tapset/64-gobject.stp:1:8 source: global gtypes [...] In this case, this error need not even be one: a single global variable can be shared between the tapset files. (If there were a type incompatibility, that would be detected separately.) Before we jump in with a big module/namespace system, let's change that error to a warning, so this case is handled similarly to the existing "cross-file global variable" situation. (Indeed, the original reported script necessarily triggers both sets of diagnostics.)
private global support moots the sort of diagnostic suggested here