[petsc-dev] Log_summary truncation behavior for long function names
Karl Rupp
rupp at iue.tuwien.ac.at
Wed Aug 5 11:33:23 CDT 2015
>> but for reasons of consistency I will also shorten the function names.
>
> That can make them inconsistent with function naming conventions, so
> don't get too crazy.
If a user looks at log_summary, finds VecVCLCopyTo, dumps that into a
search engine, and can't find a PETSc function with that name, it
certainly won't lead to excitement... But well, looks like it's still
the better thing to do, as the whole host<->device communication issue
needs to be prominently documented anyway.
Best regards,
Karli
More information about the petsc-dev
mailing list