Giovanni,
I'll see what I can do in terms of profiling the xplor-nih code
with Shark on MacOS X. However in the near term, I would strongly
urge the gcc developers to backport the changes necessary to have
-Wstrict-aliasing issue warnings for c++ in gcc 4.1. I rebuilt
xplor-nih under gcc trunk (4.2) last night and the python and tcl
interface modules (built using SWIG 1.3.22) are filled with literally
hundreds of warnings that are not shown when the swig c++ code is
compiled with gcc 4.0/4.1. It seems a shame to not provide developers
upstream with that sort of information until gcc 4.2 is released.
Jack
