<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/54125>54125</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            llvm-libgcc docs have doclinks that don't go anywhere
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            compiler-rt
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
            cjdb
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          rnk
      </td>
    </tr>
</table>

<pre>
    The [docs](https://github.com/llvm/llvm-project/blob/main/llvm-libgcc/docs/LLVMLibgcc.rst) have with [1] in them, like this:
> For example, the function __GI___backtrace eventually makes its way to a [hardcoded dlopen to libgcc_s' _Unwind_Backtrace][1]. Since libgcc_{eh.a,s.so} and libunwind have the same ABI, but different implementations, the two libraries end up [cross-talking, which ultimately results in a segfault][2].

I'm curious where those links go, I'd like to see them fixed. :)
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJyVUktvozAQ_jVwGRURHk04cGi221Wl7mkfVzTYA7gxdmSbpvn3O4ZEu9eVEHiY4XsxvZXX9udEkNRHaYVP6uekOEwhnH1SPiXFC1-jCtPSZ8LOXGj9cX88nJ19JxG47LXt-TGjMvemVv0oBFcrbPHy9vb7-9v6LnOev2lgwg-CC4NH8h0zgzIQJmL8L6DVibhQq4z8OcmfkvIrvFgH9InzWVMc4mEYFiOCsga67ttr13U9ilNwKAjog0xYUOsrzHgiDyp4uOAVggWMnBM6KawkCVLbM5nY2GR3rHgP3S9zUUZ2xztkTGeTmsEPZZjjNp7sjzRlyJp85m2yfwY0MjaXFWGzGtV6nAmejq9Rfb8EkGoYyLFOUNHUzCeMbvzdXrismhw6xQ6IsZZz1C6c9f4hoD4pM8bhy6TEBIsOasZA7NmR58rHUBE8jQNyuTkoooNbquud9exnEItTduGMJpbE7NZHg-bkYbSRIk7J25-xDLlammFQnyQzWPelSWVbyqZsMA0qaGr_2QWIm7BFwacNOEzIIVjemn1gFo7turKni9Ptf6-h8n6huGx1tSvqdGof-31Fw4B4EOLQNBIp76taiMeyL3eV2KUae9K-5UySomDos9LkHhyDxYxS1RZ5UeRlvsuruimrrKxlc0AhH-VwOOQ4JFVOvPU6i0oy68bUbZb7ZfTc1MoH_7eJ3qvREN0J32V_Y8KF83atM6d0ddGuFv4A9uIxgA">