<html>
    <head>
      <base href="http://llvm.org/bugs/" />
    </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 --- - Improve Windows long path name support"
   href="http://llvm.org/bugs/show_bug.cgi?id=21563">21563</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Improve Windows long path name support
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>libraries
          </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>normal
          </td>
        </tr>

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

        <tr>
          <th>Component</th>
          <td>Support Libraries
          </td>
        </tr>

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

        <tr>
          <th>Reporter</th>
          <td>paul_robinson@playstation.sony.com
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>llvmbugs@cs.uiuc.edu
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr></table>
      <p>
        <div>
        <pre>PR21482 (fix in r221841) addressed long path name support in the Path corner
of libSupport.  However there are also some path-name related Windows API calls
in Support/Windows/Program.inc that could benefit from the same treatment.

RedirectIO() should be updated for long path names. The widenPath() function
in Path.inc could be promoted to the path:: namespace for this purpose.

Execute() does various things; the place that handles the actual program name
should be updated for long path names, unless we decide that it would be
stupid to put an executable program in a directory where CMD.EXE couldn't
find it, and therefore in practice is not a problem. The other places that
use UTF8ToUTF16 in that function look like they're not path-related.

I looked at all other calls to UTF8ToUTF16 and they all looked like they
did not need the long-path-name treatment (uses were e.g. file encoding,
or passing environment variable names to Unicode APIs).</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>