search

harvard-acc / LLVM-Tracer

An LLVM pass to profile dynamic LLVM IR instructions and runtime values
Other
135 stars 35 forks source link

Dynamic Trace File Error #32

Closed SumantSakhalkar closed 4 years ago

SumantSakhalkar commented 4 years ago

I have observed that when I write the inputs (Main function) to the kernel in a different C file the dynamic trace file doesn't consider it. The Dynamic Trace file would just show me the labelmap and not any traces to the kernel. Am I missing something?? I am working on a docker.

xyzsam commented 4 years ago

If you changed the name of the kernel, you also need to change the value of the WORKLOAD environment variable and rebuild the instrumented binary.

Sam Xi Google Inc., Software Engineer http://www.samxi.org

On Fri, Nov 22, 2019 at 12:02 PM SumantSakhalkar notifications@github.com wrote:

I have observed that when I write the inputs (Main function) to the kernel in a different C file the dynamic trace file doesn't consider it. The Dynamic Trace file would just show me the labelmap and not any traces to the kernel. Am I missing something?? I am working on a docker.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ysshao/LLVM-Tracer/issues/32?email_source=notifications&email_token=AAKLCXGJELOXDHKORGH2WBTQVA3E3A5CNFSM4JQVLL2KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3PKHXA, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKLCXAKQ6FAZKSHHIHSBFLQVA3E3ANCNFSM4JQVLL2A .

SumantSakhalkar commented 4 years ago

I am working on the fft kernel in MachSuite Benchmark. The main function is contained in fft_test.c file and the kernel is named fft1d_512 which lies in fft.c. I have set the WORKLOAD variable to fft1D_512 and tried to rebuild the instrumented binary, but had the same issues. No traces in the dynamic_trace.gz just the labelmap.

xyzsam commented 4 years ago

Following up on old issues. Is this resolved?