Displaying 20 results from an estimated 8000 matches similar to: "llvm-lit output directory - role?"
2019 Jan 24
4
Is ist a good idea to use lit and other test tools for non llvm projects?
Hi,
I have a project which uses llvm, but is (at least not yet) a
contribution / not in the source tree of llvm.
Is it a good idea (e.g. instead of using boost test framework) to use
the llvm testsuite related tools in this case?
Alex
2019 Jan 24
3
Is ist a good idea to use lit and other test tools for non llvm projects?
On 2019-01-24 20:17, David Greene via llvm-dev wrote:
> alexp via llvm-dev <llvm-dev at lists.llvm.org> writes:
>
>> I have a project which uses llvm, but is (at least not yet) a
>> contribution / not in the source tree of llvm.
>> Is it a good idea (e.g. instead of using boost test framework) to use
>> the llvm testsuite related tools in this case?
>
>
2016 Jan 14
4
LLVM-LIT config documentation?
Dear all,
Recently I've considering using LIT for my benchmark testing framework, and
the only reference for LLVM-LIT is the man page and some READMEs. I don't
find any documentations on config, which seems to be quite important to the
tool. If I use lit outside LLVM source tree and use on my own test files,
LIT marks them as 'unresolved'.
So are there any documentations I can
2017 Sep 22
2
No longer able to run lit tests within a sub-tool
As of r313998, this workflow no longer works:
cd <build-dir>
./bin/llvm-lit <src>/llvm/tools/clang/test/CoverageMapping
I get:
llvm-lit: /Users/vk/src/llvm.org-coverage-braces/llvm/tools/clang/test/lit.cfg.py:97: note: using clang: '/Volumes/Builds/llvm.org-coverage-braces-RA/bin/clang'
llvm-lit:
2017 Sep 22
2
No longer able to run lit tests within a sub-tool
This works for me. Can you run "which clang-func-mapping" and also add a
line to clang/test/lit.cfg.py to print the value of
config.environment['PATH']?
On Fri, Sep 22, 2017 at 11:27 AM Zachary Turner <zturner at google.com> wrote:
> Looking, thanks for the report.
>
> On Fri, Sep 22, 2017 at 11:22 AM Vedant Kumar <vsk at apple.com> wrote:
>
>> As
2017 Sep 22
0
No longer able to run lit tests within a sub-tool
Looking, thanks for the report.
On Fri, Sep 22, 2017 at 11:22 AM Vedant Kumar <vsk at apple.com> wrote:
> As of r313998, this workflow no longer works:
>
> cd <build-dir>
> ./bin/llvm-lit <src>/llvm/tools/clang/test/CoverageMapping
>
> I get:
>
> llvm-lit: /Users/vk/src/llvm.org-coverage-braces/llvm/tools/clang/test/
> lit.cfg.py:97: note: using
2017 Sep 22
2
No longer able to run lit tests within a sub-tool
> On Sep 22, 2017, at 11:36 AM, Vedant Kumar <vsk at apple.com> wrote:
>
> Ah, the problem goes away once I build clang-func-mapping.
>
> I stripped some stuff out, but here's pretty much what clang/test/lit.cfg.py says my PATH is:
>
> ** PATH **: /Volumes/Builds/llvm.org-coverage-braces-RA/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
>
> I wonder how
2017 Sep 22
0
No longer able to run lit tests within a sub-tool
Ah, the problem goes away once I build clang-func-mapping.
I stripped some stuff out, but here's pretty much what clang/test/lit.cfg.py says my PATH is:
** PATH **: /Volumes/Builds/llvm.org-coverage-braces-RA/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
I wonder how this ever worked before, when I didn't have clang-func-mapping built.
Anyway, thanks for your help!
vedant
>
2014 Dec 15
3
[LLVMdev] Newbee question: LLVM backend regression tests for thumb1 targets on simulator possible?
Hello,
as a newbee, I'd appreciate some support on regression test setup.
Specifically, I am interrested in the feature of tail call optimizations for
the ARM v6m targets. This feature currently seems to be completely
deactivated at the moment (v6m being based on thumb1 ?!). According to my
code-reading, this feature will involve some modifications in epilogue
generation.
My work on a gcc
2017 Sep 22
0
No longer able to run lit tests within a sub-tool
Yea at first I was worried that maybe I changed the semantics of how it
looked in PATH, and you had clang-func-mapping in your PATH somewhere
before but now lit was building a different PATH. But I looked at that
change and it wasn't even creating that substitution before. So it looks
like that CL is indeed the problem.
On Fri, Sep 22, 2017 at 11:38 AM Vedant Kumar <vsk at apple.com>
2013 Dec 10
1
[LLVMdev] lit: deprecating trailing \ in RUN lines
On 10/12/2013 04:20, Sean Silva wrote:
> The classic way to do this sort of checking is by hacking into the
> tool that actually interprets it (i.e. lit in this case). Considering
> that lit is Python, it should be pretty easy to insert an ad-hoc regex
> check (or even something substantially more sophisticated). E.g.
> insert code into TestRunner.py's
2018 May 06
3
[clang] Running a single testcase
Hi,
while experimenting with llvmlinux on Debian/testing AMD64 I wanted to
run some x86-64 ASM tests.
I fell over [1] and wanted to run it.
So, I cloned clang from Git...
$ git clone https://github.com/llvm-mirror/clang.git
I looked through some docs where I have seen I need "llvm-lit" or "lit.py".
The Debian package llvm-7-tools from <apt.llvm.org> does ship
2012 Jan 28
1
[LLVMdev] CommandGuide documentation points to outdated pages?
Hello,
I noticed something strange in the links from
http://llvm.org/docs/CommandGuide/index.html
They all point to HTML files in http://llvm.org/cmds/, which were last
updated on 11-May-2010. There were many updates to the CommandGuide
documents since that time, according to the SVN logs, however.
One manifestation of this problem is that a fix made in r147721
(07-Jan-2012) to one of the
2020 Sep 03
2
Flakey failure on clang-ppc64le-linux-multistage
https://llvm.org/docs/CommandGuide/lit.html already lists %T as "parent
directory of %t (not unique, deprecated, do not use)". See also
https://reviews.llvm.org/D35396
On Thu, Sep 3, 2020 at 3:37 PM David Blaikie <dblaikie at gmail.com> wrote:
> Yeah, I think I'd be up for considering deprecation of %T due to the risk
> of race conditions/conflicts between tests. %t
2002 May 09
1
How do i set different permission for a shared directory?
Hello,
Would really appreciate any advise on how the security setting should be
setup.
I have running Samba ver 2.0.7 on HPUX10.20. Clients run Windows 200 PCs,
WinNT4 PDC.
"docusers" is the UNIX home directory for document users. their individual
home dir is created under their user id.
so, Paul 's home directory structure is :
/docusers/paul
Below is an extract from the
2020 Sep 03
2
Flakey failure on clang-ppc64le-linux-multistage
I think that was maybe the discussion on https://reviews.llvm.org/D78245
On Thu, Sep 3, 2020 at 6:22 PM Robinson, Paul <paul.robinson at sony.com>
wrote:
> I have a vague memory that libcxx wanted it for something, and claimed it
> would be hard to work around not having it.
>
> Anyone else remember that? I can’t dredge up the details, sorry…
>
> In any event, a separate
2013 Dec 10
0
[LLVMdev] lit: deprecating trailing \ in RUN lines
On Sun, Dec 8, 2013 at 9:04 AM, Alp Toker <alp at nuanti.com> wrote:
>
> On 08/12/2013 13:12, Chandler Carruth wrote:
>
>>
>> * Removing trailing \ will introduce the neat property that
>>>
>>> one RUN line corresponds precisely to one command that's
>>> executed. This is good for humans and will enable
2013 Dec 08
4
[LLVMdev] lit: deprecating trailing \ in RUN lines
On 08/12/2013 13:12, Chandler Carruth wrote:
>
>> * Removing trailing \ will introduce the neat property that
>> one RUN line corresponds precisely to one command that's
>> executed. This is good for humans and will enable
>> simplifications in the test runner.
>>
>> FWIW, I've never really had a
2015 Nov 14
3
[lit] RFC: Per test timeout
Hi,
A feature I've wanted in lit for a while is a having a timeout per
test. Attached
are patches that implement this idea.
I'm e-mailing llvm-dev rather than llvm-commits
because I want to gather more feedback on my initial implementation and
hopefully some answers to some unresolved issues with my implementation.
Currently in lit you can set a global timeout for
all of the tests but
2004 Aug 06
2
yp dir listing
On 4 Aug 2003 at 2:09, Karl Heyes wrote:
> On Mon, 2003-08-04 at 01:27, Arc wrote:
>
> > > There was a header mismatch, make sure that the icecast's used are
> > > recent enough first.
> >
> > I think the discussion needs to be opened as per setting a standard
> > and sticking with it. It's not just Ices/Icecast anymore, if we
> > just