search for: rforpl

...ownloads/default.profraw: Failed to uncompress data (zlib) But even for a hosted system, it is not clear to me where 'zlib' gets involved in compressing the data. The start of our data looks like: hexdump -C default.profraw 00000000 81 52 66 6f 72 70 6c ff 04 00 00 00 00 00 00 00 |.Rforpl.........| 00000010 3c 00 00 00 00 00 00 00 28 01 00 00 00 00 00 00 |<.......(.......| Which looks valid for Little-Endian, 32-bit and LLVM v4.0. What do we need to do to prepare this raw data from the device into the form that 'llvm-profdata' needs to see? Thanks, Ma...

...r a hosted system, it is not clear to me where ‘zlib’ gets >> involved in compressing the data. The start of our data looks like: >> >> >> >> *hexdump -C default.profraw* >> >> 00000000 81 52 66 6f 72 70 6c ff 04 00 00 00 00 00 00 >> >> 00 |.Rforpl.........| >> >> 00000010 3c 00 00 00 00 00 00 00 28 01 00 00 00 00 00 >> >> 00 |<.......(.......| >> >> >> >> Which looks valid for Little-Endian, 32-bit and LLVM v4.0. >> >> >> >> What do we need to do to prepare this ra...

...e ‘zlib’ gets > >> involved in compressing the data. The start of our data looks like: > >> > >> > >> > >> *hexdump -C default.profraw* > >> > >> 00000000 81 52 66 6f 72 70 6c ff 04 00 00 00 00 00 00 > >> > >> 00 |.Rforpl.........| > >> > >> 00000010 3c 00 00 00 00 00 00 00 28 01 00 00 00 00 00 > >> > >> 00 |<.......(.......| > >> > >> > >> > >> Which looks valid for Little-Endian, 32-bit and LLVM v4.0. > >> > >> > &gt...

...r a hosted system, it is not clear to me where ‘zlib’ gets >> involved in compressing the data. The start of our data looks like: >> >> >> >> *hexdump -C default.profraw* >> >> 00000000 81 52 66 6f 72 70 6c ff 04 00 00 00 00 00 00 >> >> 00 |.Rforpl.........| >> >> 00000010 3c 00 00 00 00 00 00 00 28 01 00 00 00 00 00 >> >> 00 |<.......(.......| >> >> >> >> Which looks valid for Little-Endian, 32-bit and LLVM v4.0. >> >> >> >> What do we need to do to prepare this ra...