David H. Whittington (dhw3314++at++aw101.iasl.ca.boeing.com)
Wed, 13 Mar 1996 08:46:10 -0800 (PST)
1) When running the makefile provided with perfly, all sorts of
multiply defined symbols are spewed out at the link stage - if there
are any real errors I would not easily see them. There is also a
linker command "ignore unresolved" in the makefile that hides any
real problems once you start to modify perfly to your own desires.
We have several machines around of different speed and we were able
to easily take a performer based executable around from machine to
machine but now, even when I try to link "as static as possible",
when I move to other machines, some shared objects are missing
and it vomits stuff to the screen and then dies - what a pain!
2) I was dismayed that perfly_2.0 is considerably changed in areas
from perfly_1.2 and I am unaware of any code comments, man pages,
or other documentation that provides understanding to the user about
the need for the architectural changes.I tried using the tool port2.0
on our previously working 1.2 based source and stopped after
frustration - too many significant changes, etc.
3) I will ask again - why the OPENGl version of perfly so SLOW on
a VGX machine compared to the irisgl version. I see a factor of 5
times slower on a "5-span" VGX Crimson. I could understand a 30-50%
slowdown, but this??
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:52:33 PDT