<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 - Add support for custom char8_t types with different name"
   href="https://bugs.llvm.org/show_bug.cgi?id=52324">52324</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Add support for custom char8_t types with different name
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>lldb
          </td>
        </tr>

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

        <tr>
          <th>Hardware</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>All Bugs
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>lldb-dev@lists.llvm.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>contact@lsferreira.net
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>jdevlieghere@apple.com, llvm-bugs@lists.llvm.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Currently for UTF-16 and UTF-32 types that are recognized by the DWARF encoding
tags without `char16_t` and `char32_t` names respectively are recognized, but
other names different than `char8_t` are not. To support the same behaviour of
the previous encodings, DWARF encoding tags should be taken to consideration
before fallback into the type name.

Clang TypeSystem recognizes BuiltinType::Char8 when the encoding attribute is
present but eFormatUnicode8 format is not returned in that situation, but it
should.

A patch was submitted to fix this issue: <a href="https://reviews.llvm.org/D112564">https://reviews.llvm.org/D112564</a></pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>