On Mon, Apr 09, 2018 at 07:13:00AM -0500, Crim, Jason wrote:
> I'd noticed that the cortexa8 toolchain was not available when I was starting
> to set up a new test build-environment with the latest versions. We're using
> the TI AM3352.
The v7a toolchain works just fine with this CPU. You can
Hi,
On Thu, Apr 05, 2018 at 02:41:38PM -0500, Crim, Jason wrote:
> I've got my toolchain switched to the arm-v7a-linux-gnueabihf (from the
> arm-cortexa8-linux-gnueabihf), and valgrind is now working. It complains
> about _armv7_tick being an unrecognized instruction, but my program does
>
Michael, thank you for your suggestion.
I've got my toolchain switched to the arm-v7a-linux-gnueabihf (from the
arm-cortexa8-linux-gnueabihf), and valgrind is now working. It complains about
_armv7_tick being an unrecognized instruction, but my program does continue to
run (in defiance of
Andrej,
Thanks for your information. My setup includes glibc 2.20 rather than the 2.16
referenced in your patch file, so I don't think it'll work directly (the source
of 2.20 and 2.16 look pretty different - actually, I'm not even seeing the
files referenced in the 2.16 source I pulled from
Hi Jason,
we had experienced a similar problem with the OSELAS 2012.12.1 toolchain.
In our case the problem was the missing .size directive in assembler
reimplementations of strlen and memcpy from the linaro cortex-strings patch for
glibc.
Does your "readelf -s /path/to/your/libc.so.6"
Michael,
It looks like the toolchain is configured as OSELAS.Toolchain-2014.12. I've
recently been added to a team which had this existing ptxdist setup, so I've
been trying to learn my way around ptxdist while trying to get valgrind enabled
to test an issue.
The initial run of valgrind
Hi,
On Mon, Mar 26, 2018 at 07:03:21AM -0500, Crim, Jason wrote:
> I'd tried moving over the root-debug versions of the referenced files, and
> was still hitting the error. That's when I'd found the post referencing
> the optimization levels. I'll take a look at getting the nfs-root running
>
Thanks,
I'd tried moving over the root-debug versions of the referenced files, and
was still hitting the error. That's when I'd found the post referencing the
optimization levels. I'll take a look at getting the nfs-root running when
I've got some time.
Thanks for the information and
