JuliaLang/julia

Compilation with `USE_PERF_JITEVENTS=1` fails

Open

#33,417 opened on Sep 29, 2019

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Julia (5,773 forks)batch import
Hacktoberfesthelp wanted

Repository metrics

Stars
 (48,709 stars)
PR merge metrics
 (Avg merge 20d 6h) (157 merged PRs in 30d)

Description

Platform: Ubuntu 18.04.3 LTS Tested Julia versions: v1.2.0, v1.3.0-rc2 as well as latest master (as of writing, d0365753fb57f57bcea097c05de8c07aef706561)

Adding USE_PERF_JITEVENTS=1 to Make.user results in a build error while linking against some LLVM symbol:

parallels@ubuntu /media/psf/Home/Development/julia (git)-[master] % make         
    LINK usr/lib/libjulia.so.1.4
./codegen.o: In function `jl_init_llvm':
/media/psf/Home/Development/julia/src/codegen.cpp:7761: undefined reference to `llvm::JITEventListener::createPerfJITEventListener()'
collect2: error: ld returned 1 exit status
Makefile:311: recipe for target '/media/psf/Home/Development/julia/usr/lib/libjulia.so.1.4' failed
make[1]: *** [/media/psf/Home/Development/julia/usr/lib/libjulia.so.1.4] Error 1
Makefile:75: recipe for target 'julia-src-release' failed
make: *** [julia-src-release] Error 2

Without this option, the build works fine.

Contributor guide

Research direction
Check the LLVM version being used and ensure that the 'createPerfJITEventListener' symbol is available. Verify that the build configuration includes the necessary LLVM components (e.g., 'LLVM SHARED LIBS=ON' or link against the correct LLVM library). Look at the Makefile and codegen.cpp to understand how the flag USE PERF JITEVENTS triggers the inclusion of that symbol.
Tech stack
None
Domain
build system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40