Warning when using the latest Intel PIN 3.27 version
Opened this issue · 0 comments
Hello,
This warning is possibly not important as it didn't have any impact on the core functionality of libdft64
(at least from my understanding), but just wanted to raise an issue that when I try to use the latest version of PIN (Version 3.27 https://software.intel.com/sites/landingpage/pintool/docs/98718/Pin/doc/html/index.html) with libdft, I get a warning message such as this:
...
/usr/bin/ld: warning: /home/taint_analysis/pin-3.27_build/intel64/runtime/pincrt/libc++abi.so: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010001
/usr/bin/ld: warning: /home/taint_analysis/pin-3.27_build/intel64/runtime/pincrt/libc++abi.so: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010002
/usr/bin/ld: warning: /home/taint_analysis/pin-3.27_build/intel64/runtime/pincrt/libm-dynamic.so: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010001
/usr/bin/ld: warning: /home/taint_analysis/pin-3.27_build/intel64/runtime/pincrt/libm-dynamic.so: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010002
/usr/bin/ld: warning: /home/taint_analysis/pin-3.27_build/intel64/runtime/pincrt/libc-dynamic.so: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010001
/usr/bin/ld: warning: /home/taint_analysis/pin-3.27_build/intel64/runtime/pincrt/libc-dynamic.so: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010002
/usr/bin/ld: warning: /home/taint_analysis/pin-3.27_build/intel64/runtime/pincrt/libunwind-dynamic.so: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010001
/usr/bin/ld: warning: /home/taint_analysis/pin-3.27_build/intel64/runtime/pincrt/libunwind-dynamic.so: unsupported GNU_PROPERTY_TYPE (5) type: 0xc0010002
I have tried solving this issue by myself, but after a few hours of trying to figure it out by testing with different compiler flags and such, I was unable to fix it.
I updated TAR_NAME=
in the install_pin.sh
with pin-3.27-98718-gbeaa5d51e-gcc-linux
and everything seemed to work fine until the above warning messages (which is where I dived a little bit deeper into Makefile
and other things).
I believe the issue arises from new libraries Intel PIN added (e.g., libdwarf
starting from version 3.26) which may have some conflict issue in terms of version with libdft64
. IF anyone might have solved this, that would be great to know, thank you in advance.