similar to: Usage of chmod 400 in lld lit tests causes failures when run by root user

I see many tests that are prefixed with "requires: shell". A quick search over the codebase shows 101 tests that contain this directive. This basically means there are 101 tests that say "I don't support running on Windows". I would like to get this number to 0. Ironically, many of these tests can be made to run on Windows simply by removing the requires: shell line.

Mikael, Thanks for working on. My gross comments... - Canonical URL of LLVM project is; http://llvm.org/ , not www.llvm.org. - "test-suite and cygwin" could be split out. It would be special thing. - Memory/storage requirements would be moved to "A.B Debugging". Less memory would be enough without debug build. - Python (x64 binary) is available, too. I am using. Python

Hi again, The Visual Studio getting started guide ( http://llvm.org/docs/GettingStartedVS.html) mentions the "llvm-lit" tool, but fails to mention these things: 1. Either you need to run it from bash or a similar Unix shell, as Windows does not recognize the extensionless Python script that it is. 2. Alternatively, you can invoke it using Python like this: python bin/llvm-lit

On Sat, Jun 16, 2012 at 3:29 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Takumi, > > THANK YOU for your excellent review! It makes all the work worthwhile in > itself. > > It is getting "late" here (it is early morning) so I am about to call it a > day. But I will contemplate and incorporate your suggestions tomorrow, and > send you a full

Thanks! Question about the final link step: Do I provide all the object files to the link step, i.e. something like: clang++ -o thinlto main-native.o lib/lib-native.o src/lib-native.o Do I need to provide --start-lib markers on that final link step as well? Tanoy On Tue, Jun 18, 2019 at 10:37 AM Teresa Johnson <tejohnson at google.com> wrote: > Hi Tanoy, > > You can't use

I'm trying to run distributed ThinLTO without thin archives. When I do, I get an error in the optimizer when clang tries to open a nonexistent file: clang++ -flto=thin -Xclang -fno-lto-unit -O3 -c main.cpp -o main.o clang++ -flto=thin -Xclang -fno-lto-unit -O3 -c lib/lib.cpp -o lib/lib.o clang++ -flto=thin -Xclang -fno-lto-unit -O3 -c src/lib.cpp -o src/lib.o llvm-ar -format gnu qcs lib.a

As for Ninja, I'd like to wait until it is officially part of the released CMake. As I understand it, Windows support has been checked into the CMake repository but no offical release supporting Ninja has been made yet. I just retrieved Ninja from Github and this time it built without problems. 2012/6/16 NAKAMURA Takumi <geek4civic at gmail.com> > Mikael, > > Thanks for

Now I can't make CMake use "MSYS Makefiles". I get an error about GNU v4.7.0 being broken as it can't build a simple test program. Using "MinGW Makefiles", everything works out of the box. And I am trying to give the user the most Windowsy experience (to avoid Cygwin, GnuWin32, and MSYS, if I can). So I think I'll stick to my current angle - which is to let the

Unfortunately the proposal here doesn't get rid of process creation, it just changes the process being created from a GnuWin32 one to one that we write ourselves. Happy to entertain suggestions for how to get rid of process creation entirely, but it doesn't seem simple to me. On Tue, Aug 16, 2016 at 11:20 AM Yaron Keren <yaron.keren at gmail.com> wrote: > You can use msys2

That's only if you use git bash, not cmd. On Tue, Aug 16, 2016 at 11:38 AM Reid Kleckner <rnk at google.com> wrote: > One other thing to note is that the dependency problem is going to go away > very soon just a result of moving to git. The normal Windows install of git > comes with all the utilities you need to run the LLVM tests anyway. I > haven't bothered to install

I am trying to work through the usage of thinlto for distributed builds. Here is the simple thinlto usage, just add -flto=thin everywhere, easy: clang++ -flto=thin -O3 -c -o CreateWay_.o -DSPEC_CPU -DNDEBUG -DSPEC_CPU_LITTLE_ENDIAN -Wno-dangling-else CreateWay_.cpp clang++ -flto=thin -O3 -c -o Places_.o -DSPEC_CPU -DNDEBUG -DSPEC_CPU_LITTLE_ENDIAN

Oh, didn't realize that there already is a semi-official build of CMake with Ninja support. I am trying it out right now and it seems very promising. So I'll change the document to use Ninja instead of "MinGW Makefiles". No need to waste energy on MinGW and MSYS Makefiles when Ninja outdoes them both. I thought people would have to build CMake themselves, something I'd

Thanks Teresa Yes it is astar, happen to send a tar of the sources but they are just copies from the spec distribution The ld command is: GNU ld (GNU Binutils) 2.29.1 Thanks for the guidance on path names. The prefix-replace just effects the string written to the object files right? So we could post-process that file with other tools as well, correct? Thanks again --david From: Teresa Johnson

Hi Takumi, THANK YOU for your excellent review! It makes all the work worthwhile in itself. It is getting "late" here (it is early morning) so I am about to call it a day. But I will contemplate and incorporate your suggestions tomorrow, and send you a full reply. I think I originally wrote a document where I addressed both Visual Studio and MinGW, but then decided that there were

That's more like a workaround though. The real problem is that file deletion is racy on Windows. I can't count the number of times I've encountered this error, only to find out that adding a retry fixed the problem. Sure, if you can remove opened files then there's no problem to begin with, but even if you can't, you can still remove the file by retrying again 100ms later or

Fails with gold too: Library-native.o:Library.cpp:regway: error: undefined reference to 'vtable for regwayobj' /home/dcallahan/fbsource/fbcode/third-party-buck/platform007/tools/binutils/bin/gold/ld: the vtable symbol may be undefined because the class is missing its key function clang-8: error: linker command failed with exit code 1 (use -v to see invocation) From: Teresa Johnson

> > Anecdotally, most of the times I've seen people add "REQUIRES: shell" on > a test they really meant "disable on windows". I think/hope that's > usually temporary while they investigate problems, but it might explain > why so many tests say they require shell when they don't. > > In at least one case I can think of

For those interested in the actual file, it is now attached. ---------- Forwarded message ---------- From: Mikael Lyngvig <mikael at lyngvig.org> Date: 2012/6/16 Subject: RFC: "Building with MinGW on Windows" (DOC, NEW) To: LLVMdev Mailing List <llvmdev at cs.uiuc.edu> Here's the first part of my Windows set up documentation. This one only covers the process of

On Fri, May 15, 2015 at 12:02 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > > On 2015-May-15, at 07:30, Teresa Johnson <tejohnson at google.com> wrote: > > > >>> a. Lazy Debug Metadata Linking: > >>> > >>> The prototype implementation included lazy importing of module-level > >>> metadata during the

I'm using Windows 8.1, and every time I run check-clang, I eventually end up with a bunch of hung processes. Generally this is an instance of clang.exe, a bunch of instances of FileCheck.exe, and occasionally an llc.exe and an opt.exe. Inside, the processes are all hung inside of calls to WriteFile() attempting to write to stdout. I notice some of the tests fail with output indicating that