<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 - _LIBCPP_INLINE_VISIBILITY doesn't always hide the symbols (Ex. __emplace_back_slow_path)"
   href="https://bugs.llvm.org/show_bug.cgi?id=41490">41490</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>_LIBCPP_INLINE_VISIBILITY doesn't always hide the symbols (Ex. __emplace_back_slow_path)
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>libc++
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>PC
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </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>All Bugs
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>unassignedclangbugs@nondot.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>eric@efcs.ca
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>llvm-bugs@lists.llvm.org, mclow.lists@gmail.com
          </td>
        </tr></table>
      <p>
        <div>
        <pre>The `inline` keyword placed on the declarations on `__push_back_slow_path` and
`__emplace_back_slow_path` is needed to prevent them from appearing in
libc++.so's dynamic symbol table (for instantiations used inside the library). 

However, they are marked also given hidden visibility, which should prevent
this in the first place.

Adding `inline` is problematic for two reasons:

1) It's not a real fix.
2) It can needlessly increase the binary size of users (because clang actually
uses `inline` as an inlining hint).

The second problem cause chrome to have a 1% binary size increase.

We should investigate why Clang is not hiding this symbol. We should also
seriously consider moving to explicit export lists.

@Louis, any thoughts?</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>