similar to: [LLVMdev] Testing with llvm-lit

2010/11/8 Brice Lin <brice.lin at gmail.com>: > $ ~/llvm/Debug+Asserts/bin/llvm-lit ~/llvm/test/Integer/BitCast.ll > llvm-lit: lit.cfg:103: fatal: No site specific configuration available! Have you ever run "make check" and passed? ...Takumi

Ping, NAKAMURA san, thank you. Bill san, can you comment this commit? r154798 still fails on ppc32-lnux b/c *only* for this test. Loving more minor arch, the world will be better... 2012/04/04 23:26 NAKAMURA Takumi <geek4civic at gmail.com>: > Kimura san, > > You may ask committer of r153706. I wonder if it could be x86-independent. > >>

Kimura san, You may ask committer of r153706. I wonder if it could be x86-independent. > /var/tmp/portage/sys-devel/llvm-9999/work/llvm-9999/Release/bin/llc: > error auto-selecting target for module 'No available targets are > compatible with this triple, see -version for the available targets.'. >  Please use the -march option to explicitly pick a target. ...Takumi as

Hi, CodeGen/Generic/dbg-declare.ll is really generic test? $ make check llvm[0]: Running test suite make[1]: Entering directory `/var/tmp/portage/sys-devel/llvm-9999/work/llvm-9999/test' Making a new site.exp file... Making LLVM 'lit.site.cfg' file... Making LLVM unittest 'lit.site.cfg' file... ( ulimit -t 600 ; ulimit -d 512000 ; ulimit -m 512000 ; ulimit -v 1024000 ; \

Morning, Will! 2012/7/12 Will Schmidt <will_schmidt at vnet.ibm.com>: > llvm]$ gmake check > llvm[0]: Running test suite > gmake[1]: Entering directory `/home/willschm/llvm/test' > Making LLVM 'lit.site.cfg' file... > sed: file lit.tmp line 8: unknown option to `s' > gmake[1]: *** [lit.site.cfg] Error 1 > > The relevant lines in test/Makefile: >

Hi, Using trunk llvm ; on powerpc (powerpc64/power7); trying to do a "gmake check", the sed bits in test/Makefile appear to be getting tripped up when trying to generate lit.site.cfg. I've started to hack at it, made a little bit of progress, but wonder if I'm just digging myself a hole. Highlights of what I've poked at are below.. Comments or thoughts? Thanks,

2012/6/16 Justin Holewinski <justin.holewinski at gmail.com>: > Under Python installation, you mention that Python is only needed for the > test suite.  This is not true, as the normal LLVM build still requires > Python. That's right. Now, python>=2.4 is essential. (In contrast, perl is not required, IIRC) > I would seriously consider splitting this up into

I have been working for extending test coverage for years. Nowadays, I have several cross-testing (target != host). See http://bb.pgr.jp/console Each of them (test-*-linux) is doing; - Assume a preceding builder passes with warming ccache. - All compilation units will hit ccache whenever the tree is built before lit. - Almost all compilation units will hit ccache except for Host.cpp when

Good morning David, I won't accept your patches for now. It breaks lots of things in current environments, autoconf - msys, cmake - msys, cmake -mingw and cmake - msvs. - You should never forget other environments. (eg., MSYS and CMD.EXE) You should implement detecting MKS if you tweak MKS-specific stuff. - Bash should be assumed to be mature. I suppose MKS bash might be

On 26 November 2013 01:55, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > IMHO, tests may be suppressed with lit.local.cfg, only if; > They were disabled, but then re-enabled because they don't fail on normal build bots, but they do on self-host bots. So, I think this is a more serious issue than just MCJIT, I think this is a Clang miscompilation. I'll try on x86 to see

I have filed a number of problem reports about getting the LLVM test infrastructure working for an environment with: Windows + MSVC9 + Cmake + NMake makefiles + MKS. (MKS provides unix-like tools for Windows, but based on very old versions, so they have quirky or minimal compatibility with GNU tools.) http://llvm.org/bugs/show_bug.cgi?id=9689 - Fix Cmake generation of compile_cxx for MSVC -

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

2012/9/13 Kaylor, Andrew <andrew.kaylor at intel.com>: > I'm a bit confused as to what is supposed to happen in the cross building scenarios. For instance, if host=x86_64-linux and target=i686-mingw32, what should the MCJIT tests do? Should they be suppressed because the architectures don't match? If so, what about the case where host=x86_64-linux and target=x86_64-mingw32?

IMHO, tests may be suppressed with lit.local.cfg, only if; - The issue is filed -- PR18057 - There is at least one person responsible to watch on this issue. Suppression is not good idea. But it should be done anyways if responsible person were there. I would not help you since I don't have any arm boxes. Thank you. 2013/11/26 Renato Golin <renato.golin at linaro.org>: > Hi

Galina and Takumi, Are we ready to update the minimum required version to 2.8.12.2? -Chris > On Feb 12, 2015, at 2:35 PM, Chris Bieneman <beanz at apple.com> wrote: > > Chandler's feedback was that we should go to 2.8.12.2 instead of 3.0 because of Ubuntu's LTS release. > > -Chris > > > > On Feb 12, 2015, at 11:29 AM, Galina Kistanova <gkistanova

I'm with Takumi, and prefer to go on a safe route. Takumi, unless I'm missing something you were checking cmake 3.x with LLVM. How does it look like? Did you discover any problem? Thanks Galina On Mon, Feb 9, 2015 at 4:28 PM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > I missed the context. We may stand on 2.8.12.2 at first. > > I will update my cmake from

No, it has the wrong value. I tried it with cmake 2.8.9 and 2.8.12.2. Both of them set the variable to “.so”. On Feb 12, 2014, at 5:29 PM, NAKAMURA Takumi <geek4civic at gmail.com> wrote: > Juergen, > > Thanks to let me know. I guess r200762 (and r200763) might affect. > > Although I won't check this on darwin box, I suspect the line in > HandleLLVMOptions.cmake;

Hello, NAKAMURA Takumi As you said, I check out the head from svn trunk. I build the source code as the following steps: $./configure --enable-shared $ make After 1 hour, the building procedure is stopped and appear the following error message: c:/strawberry/c/bin/../lib/gcc/i686-w64-mingw32/4.4.3/../../../../i686-w64-mingw 32/bin/ld.exe:

Hi Andrew & Takumi, I'm including you guys because you seem to know what should and what shouldn't work, given your recent changes to the XFAILs. Feel free to exclude yourselves, or include other folks. I'm having a problem with a self-hosting ARM bot described here: http://llvm.org/bugs/show_bug.cgi?id=18057 Basically, allocateSpace() sometimes works, sometimes doesn't. I

Good evening, Yuan Excuse me, I gave up Debug build earlier due to my poor hosts. I will improve able to build Debug ;) You may build with --enable-optimized=yes (or, make ENABLE_OPTIMIZED=1) btw, DLL builder has implemented since Aug. It might be easier to port DLL stuff to 2.6 :) Do you try? ...Takumi 2010年9月2日 17:16:25 UTC+9 yuan zheng <tsinghuayuan86 at gmail.com>: > Hello,