On Wed, Nov 28, 2012 at 1:53 PM, Roy Stogner <royst...@ices.utexas.edu>wrote:
> No it didn't. Those are two separate methods - the former is for
> gprof-style user-space profiling, the latter is for oprofile-style
> hardware-interrupt-based profiling.
>
Ah OK. Well, I don't prof in the case "${METHOD}" block in
libmesh_method.m4 and I got a configure error with METHOD=prof so I'd
assumed it had just been changed. In that case, I've changed the patch to
keep oprofile as the method name and corrected the Makefile generation. OK
for trunk?
method.patch
Description: Binary data
------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: INSIGHTS What's next for parallel hardware, programming and related areas? Interviews and blogs by thought leaders keep you ahead of the curve. http://goparallel.sourceforge.net
_______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
