OProfile support is disabled

Bug #1148529 reported by Ryo Onodera
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
llvm-3.1 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

OProfile suppot for LLVM is disabled. It is used for profiling JIT-ed code by LLVM.

Please enable OProfile. I created a rough patch for it. Please review.

Tags: patch
Revision history for this message
Ryo Onodera (ryoqun) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "llvm-oprofile.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch
Revision history for this message
Sylvestre Ledru (sylvestre) wrote :

Next time, please report that into the debian bug tracker.

Any side effects or performance issues we should expect from it ?

Revision history for this message
Ryo Onodera (ryoqun) wrote :

Thanks for replying!

First of all, Ubuntu started to provide the latest OProfile (0.9.8) again after some inactivity of packaging. I'm really happy about that. Thank you very mcuh!!

Because now LLVM depends on libopagent, this bug is blocked by these following libopagent-related bugs:

Bug 1154025 Install PIC version of libbfd.a
Bug 1148682 symbol lookup error: /usr/lib/libopagent.so: undefined symbol: bfd_init

Could you also take a look at these? By resolving them, we can avoid to add the linking option "-lbfd" to configure.

Turning back to this bug, the side effects or permance issues should be minimal.

When LLVM's users aren't using OProfile related C++ LLVM classes explitly, nothing happens at runtime. Thus, thre is no performance degragation at all. Starting from LLVM 3.1, linking to libopagent is delayed by using dlopen as much as possible until when we absoluteby have to do it.

In a sense, as a side effect, we have new dependancy. Also, the binary size will be bigger a bit.

Note that I didn't but we should make libllvm3.1 and llvm-3.1-dev depend on libopagent1.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in llvm-3.1 (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.