Hello, On Tuesday 13 September 2011 12:27:16 Tanguy Bouzeloc wrote: > Hello, > > I prepare a valgrind-mips package and it seems okay for bcm63xx target > with uclibc. > > It requires gcc 4.4+ in order to build and I've to force -01 > optimisation level > (Os or -O2 eventually freeze gcc).
Are you sure this is working? valgrind does not repport any memory allocation for me, which looks suspicious to me. This was tested on malta+uclibc. Otherwise, you can just provide a patch which updates the existing valgrind package, there is no need to create a specific valgrind-mips package. Thank you. > > Regards, > Tanguy. > > On 09/06/2011 05:37 PM, Raphaël HUCK wrote: > > Hi all, > > > > I've just stumbled upon a patch adding MIPS support to Valgrind. It is > > applicable for MIPS32r2 instruction set, and supports both little-endian > > and big-endian cores. > > > > It can be applied to the revision 11845 (version 3.7.0.SVN) from the > > main Valgrind trunk. > > > > However, as the Valgrind package in OpenWrt > > (https://dev.openwrt.org/browser/packages/utils/valgrind/Makefile) uses > > version 3.3.1, how is it possible to package Valgrind/MIPS for OpenWrt > > without conflicting with the existing package? > > > > For those who are interested in this patch, see > > https://bugs.kde.org/show_bug.cgi?id=270777#c12 > > > > Thanks, > > > > -Raphael > > _______________________________________________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Florian _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
