<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Allow selecting which XRay modes to link through flags"
href="https://bugs.llvm.org/show_bug.cgi?id=37066">37066</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Allow selecting which XRay modes to link through flags
</td>
</tr>
<tr>
<th>Product</th>
<td>XRay
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Clang
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dberris@google.com
</td>
</tr>
<tr>
<th>Reporter</th>
<td>dberris@google.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org
</td>
</tr></table>
<p>
<div>
<pre>When building with the default XRay runtime, we're packaging all known
implementations that are part of the compiler-rt XRay runtime. While this is
convenient, there are environments where we might want to not actually link any
of these implementations due to a number of concerns (code size increase due to
unused modes, tighter control of dependencies that make it into binaries as
XRay evolves, etc.).
The suggestion is to add a clang flag `-fxray-modes=` which accepts a
comma-separated list of modes, and simultaneously add individual link targets
in compiler-rt's xray implementation to build different archives for those
modes. This effectively decouples the XRay modes into self-contained archives.
It also provides an additional means of distributing platform-specific or
custom modes that build upon the XRay framework.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>