This issue isn't totally just that. LIBGL_ALWAYS_SOFTWARE=true mode does use
LLVM doesn't it? And I find profiling information trailing from a perf-foo.map
file that seems to correspond to JITted code. So, I think this is still valid
for LIBGL_ALWAYS_SOFTWARE=true mode. I was mistaken for unset
the functionality or maybe something has
to be done to notify profilers about it (similar to how Valgrind and
such need to be notified about JITted code.)
Thank you,
Steven Stewart-Gallus
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http
is a bug in
perf (they've had problems with artificial intrinsics before.) Please assume I
have at least the small quantity of intelligence needed to have installed the
debugging symbols for the library I a. But tell me, what do you see when you
profile glxgears with perf?
Thank you,
Steven Stewart
Okay,
| glxinfo
name of display: :0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
GLX_ARB_create_context, GLX_ARB_create_context_profile,
GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float,
information as the
JITted code has no debug information.
Thank you,
Steven Stewart-Gallus
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
abilities?
Thank you,
Steven Stewart-Gallus
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
