On Wed, Jun 9, 2010 at 11:11 PM, Nathan Jeffords <blunted2night at gmail.com> wrote:> This is cool, I was looking into something like this, but hit a little bit > of a wall, and then got sidetracked on another project. I was going to use > llc to generate COFF object files as opposed to clang. Seems to me llc would > give better control over what was generated and would also not require clang > to be in the tree. > Is there any documentation on how to run these tests from windows?I just tried to actually run the tests in llvm/test (as opposed to llvm/tools/clang/test) and none of them work on windows. They all fail due to windows using \ for directories, which the test runner seems to want to use as an escape sequence. What I don't get is how clang tests run fine on windows, but not llvm tests. And why I have not seen this problem posted anywhere. - Michael Spencer
On Thu, Jun 10, 2010 at 2:41 AM, Bigcheese <bigcheesegs at gmail.com> wrote:> On Wed, Jun 9, 2010 at 11:11 PM, Nathan Jeffords > <blunted2night at gmail.com> wrote: >> This is cool, I was looking into something like this, but hit a little bit >> of a wall, and then got sidetracked on another project. I was going to use >> llc to generate COFF object files as opposed to clang. Seems to me llc would >> give better control over what was generated and would also not require clang >> to be in the tree. >> Is there any documentation on how to run these tests from windows? > > I just tried to actually run the tests in llvm/test (as opposed to > llvm/tools/clang/test) and none of them work on windows. They all fail > due to windows using \ for directories, which the test runner seems to > want to use as an escape sequence. > > What I don't get is how clang tests run fine on windows, but not llvm > tests. And why I have not seen this problem posted anywhere. > > - Michael Spencer >I poked around, and after applying the attached patch, some tests run just fine. (test's with grep and spaces are broken as are some others). Here's how I run the test I wrote: C:\Users\Michael\Projects\llvm>"C:\Python26\python.exe" C:/Users/Michael/Proj ects/llvm/utils/lit/lit.py --param llvm_site_config=C:/Users/Michael/Projects /llvm-build/VS9/test/lit.site.cfg --param llvm_unit_site_config=C:/Users/Mich ael/Projects/llvm-build/VS9/test/Unit/lit.site.cfg -v C:/Users/Michael/Pro jects/llvm-build/VS9/test/MC/COFF/basic-coff.s - Michael Spencer -------------- next part -------------- A non-text attachment was scrubbed... Name: test.patch Type: application/octet-stream Size: 19406 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100610/847c289c/attachment.obj>
On Thu, Jun 10, 2010 at 1:43 AM, Bigcheese <bigcheesegs at gmail.com> wrote:> On Thu, Jun 10, 2010 at 2:41 AM, Bigcheese <bigcheesegs at gmail.com> wrote: >> On Wed, Jun 9, 2010 at 11:11 PM, Nathan Jeffords >> <blunted2night at gmail.com> wrote: >>> This is cool, I was looking into something like this, but hit a little bit >>> of a wall, and then got sidetracked on another project. I was going to use >>> llc to generate COFF object files as opposed to clang. Seems to me llc would >>> give better control over what was generated and would also not require clang >>> to be in the tree. >>> Is there any documentation on how to run these tests from windows? >> >> I just tried to actually run the tests in llvm/test (as opposed to >> llvm/tools/clang/test) and none of them work on windows. They all fail >> due to windows using \ for directories, which the test runner seems to >> want to use as an escape sequence. >> >> What I don't get is how clang tests run fine on windows, but not llvm >> tests. And why I have not seen this problem posted anywhere. >> >> - Michael Spencer >> > > I poked around, and after applying the attached patch, some tests run > just fine. (test's with grep and spaces are broken as are some > others).The lit specific portion of your patch isn't right. LLVM tests are written in a Tcl style. What we need to do is find a way to make lit agnostic to the Windows paths. This probably comes down to normalizing the %s etc subtitutions to Unix style, then translating the paths to Windows style when we actually execute commands. - Daniel> Here's how I run the test I wrote: > > C:\Users\Michael\Projects\llvm>"C:\Python26\python.exe" C:/Users/Michael/Proj > ects/llvm/utils/lit/lit.py --param llvm_site_config=C:/Users/Michael/Projects > /llvm-build/VS9/test/lit.site.cfg --param llvm_unit_site_config=C:/Users/Mich > ael/Projects/llvm-build/VS9/test/Unit/lit.site.cfg -v C:/Users/Michael/Pro > jects/llvm-build/VS9/test/MC/COFF/basic-coff.s > > - Michael Spencer > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >
On Wed, Jun 9, 2010 at 11:41 PM, Bigcheese <bigcheesegs at gmail.com> wrote:> On Wed, Jun 9, 2010 at 11:11 PM, Nathan Jeffords > <blunted2night at gmail.com> wrote: >> This is cool, I was looking into something like this, but hit a little bit >> of a wall, and then got sidetracked on another project. I was going to use >> llc to generate COFF object files as opposed to clang. Seems to me llc would >> give better control over what was generated and would also not require clang >> to be in the tree. >> Is there any documentation on how to run these tests from windows? > > I just tried to actually run the tests in llvm/test (as opposed to > llvm/tools/clang/test) and none of them work on windows. They all fail > due to windows using \ for directories, which the test runner seems to > want to use as an escape sequence. > > What I don't get is how clang tests run fine on windows, but not llvm > tests. And why I have not seen this problem posted anywhere.No one has made it work yet, it's that simple. - Daniel> > - Michael Spencer > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
Here's a (more) proper patch for getting the tests to run on windows. With this only ~250 tests Unexpected Fail. I just need someone to make sure it doesn't break anything on other platforms. It feels kind of hacky, and I would appreciate any ideas on improvements. http://codereview.appspot.com/1657041/show - Michael Spencer