[Mesa-dev] How difficult would it be to have debugging information for Jitted code show up?

[Jose Fonseca]

> And I find profiling information trailing from a perf-foo.map file that seems to correspond to JITted code.

Yep. That sounds like llmvpipe. See http://mesa3d.org/llvmpipe.html for details.

But note that have "source lines" for jit code is hard:
- Some of the LLVM IR we generate comes from TGSI which has no source line info.  We could have the info from the GLSL, but that has no source files. . 
- Some of TGSI doesn't come from GLSL, but rather fixed function.
- Some of the LLVM IR doesn't even come from TGSI or any shaders, but  its bound state like depth-stencil test, or format conversion.  None of that IR has source files.  We could use the debug info from the C code that generates the LLVM IR that generates the . 

In short, we could try to improve things a bit, but JIT code will always be quite different from static C code.

Jose

________________________________________
From: mesa-dev <mesa-dev-bounces at lists.freedesktop.org> on behalf of Steven Stewart-Gallus <sstewartgallus00 at mylangara.bc.ca>
Sent: 14 November 2014 19:23
To: Emil Velikov
Cc: ML mesa-dev
Subject: Re: [Mesa-dev] How difficult would it be to have debugging information for Jitted code show up?

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
LIBGL_ALWAYS_SOFTWARE though I think.
_______________________________________________
mesa-dev mailing list
mesa-dev at lists.freedesktop.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_mailman_listinfo_mesa-2Ddev&d=AAIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=zfmBZnnVGHeYde45pMKNnVyzeaZbdIqVLprmZCM2zzE&m=IVw7I-5WEvdqar1LGKpNSi56XoZMlsmzcc5IKTLmvYA&s=iCS5PuoCjw1nnf0AgSWX0cNGwCa1NET5erjzE8lrX8U&e=