search for: bodytrack

I've recently played with the GCC implementation of pointer checker on a real hardware, my recent impressions are here: https://github.com/google/sanitizers/wiki/AddressSanitizerIntelMemoryProtectionExtensions (there is also some old pre-hardware content). In short, I totally agree with what David says above: MPX is a disaster. (Usual disclaimer: my opinion here is too biased) I am glad

Hi,all I ran my generated whole-program bitcode file which performs as a bodytrack tool, it can give me the right result but with a stack dump before it exsits Update Error : Model observation failed for time : 1 Error loading observation data terminate called after throwing an instance of 'std::bad_cast' what(): std::bad_cast 0 lli 0x08b713d2 1 lli...

...chmark suite is PARSEC 3.0, all versions with 1 thread and default > configs. > > As I described previously, PointerChecker in gcc produces very > inefficient code. My experiments show overheads over native of up to > 9.5X (on "raytrace"), with common overheads of 3X ("bodytrack", > "fluidanimate", "streamcluster"). At the same time, AddressSanitizer > performs much better -- 1.3X on "raytrace", 1.7X on "bodytrack" and so > on. > > Recently I played with MPX support on Intel C/C++ Compiler (icc). This > impleme...

...--------------------------------------------------------------------------------------+ | blks | _Z19BlkSchlsEqEuroNoDivfffffif | +-----------------+----------------------------------------------------------------------------------------------+ | bodytrack | _ZN17ImageMeasurements11InsideErrorERK17ProjectedCylinderRK11BinaryImageRiS6_ | +-----------------+----------------------------------------------------------------------------------------------+ | bzip2 | BZ2_compressBlock |...

...-----------------------------------------+ > > | blks | _Z19BlkSchlsEqEuroNoDivfffffif > > | > > > +-----------------+----------------------------------------------------------------------------------------------+ > > | bodytrack | > > > _ZN17ImageMeasurements11InsideErrorERK17ProjectedCylinderRK11BinaryImageRiS6_ > > | > > > +-----------------+----------------------------------------------------------------------------------------------+ > > | bzip2 | BZ2_compres...

...------------------------------------------------------------------+ > | blks | _Z19BlkSchlsEqEuroNoDivfffffif > | > +-----------------+----------------------------------------------------------------------------------------------+ > | bodytrack | > _ZN17ImageMeasurements11InsideErrorERK17ProjectedCylinderRK11BinaryImageRiS6_ > | > +-----------------+----------------------------------------------------------------------------------------------+ > | bzip2 | BZ2_compressBlock >...

...itrii Kuvaiskii < Dmitrii.Kuvaiskii at tu-dresden.de> wrote: > >> Recently I played with MPX support on Intel C/C++ Compiler (icc). This > >> implementation looks *much* better, with the following example > >> overheads: 1.2X on "raytrace", 1.25X on "bodytrack", 1.08X on > >> "streamcluster". So the common overheads are in the range of 15%-25%! > > That's interesting. > > Are you sure you are instrumenting both reads and writes with icc? > > Yes, here are the exact flags I add to the usual build configuration...

Hi Nan Zhu, > I use Bugpoint to check it , Bugpoint gives me the following information: > > > Read input file : 'bodytrack.bc' > *** All input ok > Initializing execution environment: Found gcc: /usr/lib/ccache/gcc > Running the code generator to test for a crash: <cbe>*** Debugging code > generator crash! > > Error running tool: > /usr/local/bin/llc -o bugpoint-test-program.bc.cbe.c...

...----------------+ >> > | blks | _Z19BlkSchlsEqEuroNoDivfffffif >> > | >> > >> > +-----------------+----------------------------------------------------------------------------------------------+ >> > | bodytrack | >> > >> > _ZN17ImageMeasurements11InsideErrorERK17ProjectedCylinderRK11BinaryImageRiS6_ >> > | >> > >> > +-----------------+----------------------------------------------------------------------------------------------+ >> &g...

...+---------------+-----------+--------------+----------+ | blks | 2 | 0m1.036s | 0m1.008s | 2 | 0m3.643s | 0m3.205s | 155931 | 155459 | +---------------+----------+-------------+-----------+-----------+---------------+-----------+--------------+----------+ | bodytrack | 29 | 0m4.907s | 0m4.881s | 5 | 0m14.786s | 0m1.943s | 2125256 | 2124224 | +---------------+----------+-------------+-----------+-----------+---------------+-----------+--------------+----------+ | bzip2 | 60 | 0m1.274s | 0m1.268s | 3 | 0m...

...aiskii at tu-dresden.de> wrote: >> >>> >> Recently I played with MPX support on Intel C/C++ Compiler (icc). This >>> >> implementation looks *much* better, with the following example >>> >> overheads: 1.2X on "raytrace", 1.25X on "bodytrack", 1.08X on >>> >> "streamcluster". So the common overheads are in the range of 15%-25%! >>> > That's interesting. >>> > Are you sure you are instrumenting both reads and writes with icc? >>> >>> Yes, here are the exact flag...

...gt;>/Recently I played with MPX support on Intel C/C++ Compiler (icc). />>>>>>>>/This />>>>>>>>/implementation looks *much* better, with the following example />>>>>>>>/overheads: 1.2X on "raytrace", 1.25X on "bodytrack", 1.08X on />>>>>>>>/"streamcluster". So the common overheads are in the range of />>/15%-25%! />>>>>>>/That's interesting. />>>>>>>/Are you sure you are instrumenting both reads and writes with icc? />&gt...

This proposal adds support for path profiling [Ball96] to LLVM. Path profiling compactly represents acyclic paths in a directed acyclic graph representation of the control flow graph of a routine. Instrumentation can be added to uniquely identify paths executed at runtime. Path profiles enable precise enumeration of the sequence of basic blocks executed in order for a particular path. Using path