Displaying 3 results from an estimated 3 matches for "renamepathondisk".
2006 May 07
2
[LLVMdev] The Next Win32 File System Problem
...;
The result:
C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: Can't move './libgcc.a-000003' to './libgcc.a-000002': Cannot create a file when that file already exists.
So apparently, we're trying to move one file on top of another.
The error is generated in:
Path::renamePathOnDisk(const Path& newName) {
if (!MoveFile(path.c_str(), newName.c_str()))
ThrowError("Can't move '" + path +
"' to '" + newName.path + "': ");
return true;
}
I'm guessing that the last part of the error message ("Cann...
2006 May 07
0
[LLVMdev] The Next Win32 File System Problem
...0\home\llvm_home\install\bin\llvm-ar.exe: Can't move './libgcc.a-000003' to './libgcc.a-000002': Cannot create a file when that file already exists.
>
> So apparently, we're trying to move one file on top of another.
>
> The error is generated in:
>
> Path::renamePathOnDisk(const Path& newName) {
> if (!MoveFile(path.c_str(), newName.c_str()))
> ThrowError("Can't move '" + path +
> "' to '" + newName.path + "': ");
> return true;
> }
>
> I'm guessing that the last par...
2007 Jul 05
2
[LLVMdev] PATCH (rest of code changes) "bytecode" --> "bitcode"
Here is the bulk of the sanitizing.
My residual doubts center around the question
whether we still do/want to support (un)compressed *byte*code
in 2.0/2.1.
I need a definitive word on this to proceed.
My understanding is that bytecode is already gone, but there are
still some functions/enums that really deal with *byte*code
(instead of *bit*code).
I did not touch those areas, so the attached