<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 - Trigraph support in various C language modes"
   href="https://bugs.llvm.org/show_bug.cgi?id=47645">47645</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Trigraph support in various C language modes
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>clang
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>trunk
          </td>
        </tr>

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

        <tr>
          <th>OS</th>
          <td>Windows NT
          </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>C
          </td>
        </tr>

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

        <tr>
          <th>Reporter</th>
          <td>aaron@aaronballman.com
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>blitzrakete@gmail.com, dgregor@apple.com, erik.pilkington@gmail.com, llvm-bugs@lists.llvm.org, richard-llvm@metafoo.co.uk
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Clang's trigraph support is disabled by default when the language standard is
set to GNU C mode. Not supporting trigraphs is perhaps reasonable because the
user is specifying that they want something other than standard C.

However, when *no* -std= option is passed on the command line, we silently
default to gnu17 mode which then disables this standard C feature and that
seems less reasonable to me because this is a case where we're *removing*
support for a feature rather than adding a conforming extension. The user is
saying "here's my C file, please compile it" and I think we should be able to
compile conforming C in that case (for some C standard version, but all of them
currently support trigraphs).

Confounding matters somewhat, we define __STDC__ to 1 in GNU mode despite
trigraph support in C being mandatory.

Should trigraphs remain enabled when no -std is present (even though we would
still default to gnu17) so that users can compile conforming C code?
Should __STDC__ be paying attention to whether trigraph support is enabled or
not?</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>