[Openmp-dev] testsuite script error
Carlo Bertolli
cbertol at us.ibm.com
Thu May 14 20:19:19 PDT 2015
Hi Millad
Thanks for your answer, now I see what is happening.
However, please correct me if I am saying something wrong, I see that
these .ll files are generated by the Makefile in the testsuite/bin/
directory.
When I run "make test" in runtime, I get the following errors at the end,
after all tests have been compiled and run:
Makefile:19: recipe for target 'c/orph_ctest_omp_parallel_default' failed
make[2]: *** [c/orph_ctest_omp_parallel_default] Error 1
In file included from c/test_omp_get_wtick.c:4:
c/omp_testsuite.h:11:10: fatal error: 'omp.h' file not found
#include <omp.h>
^
1 error generated.
and similar..
I guess this is because the setting of the include path is not working (at
least on my machine). What is the right place to fix it?
testsuite/bin/Makefile? Should I fix it by hand before running make test
(in the sense that right now "make test" seems to do all the work for me)?
Also, running "make test" in runtime/ fills up my testsuite/ directory
with .log files. Is this expected? Incidentally, the .log files for
orphaned tests seem to be failing a lot (if not them all).
Thanks and apologies if I am missing some of the point
-- Carlo
From: Millad Ghane <millad.mg at gmail.com>
To: Carlo Bertolli/Watson/IBM at IBMUS
Cc: Sunita Chandrasekaran <sunita at cs.uh.edu>,
"openmp-dev at dcs-maillist2.engr.illinois.edu"
<openmp-dev at dcs-maillist2.engr.illinois.edu>, sunita
chandrasekaran <sunisg123 at gmail.com>
Date: 05/14/2015 08:46 PM
Subject: Re: [Openmp-dev] testsuite script error
Hi Carlo,
I am responding on behalf of Sunita.
The "make test" command in the runtime folder does not only do the "make
ctest". The "make ctest" here actually tries to generate the LL files. And,
these LL files are consumed afterwards by llvm-lit command to see whether
the test is passed or not. So, "make test" command is not solely "make
ctest" and the test part happens with another command. We did provide this
rule, "make test", to make your life easier.
The peace of code that you mentioned is actually generating the LL files.
At first, we proposed to put the testing rule (make test) in the testsuite.
However, it was rejected. So, we tried to include it in the runtime folder
for sake of OpenMP testers.
And make -j: Simply, it tries to build a package with multiple jobs in
parallel in order to speedup building. For example, with (make -j 8), we
are trying to speedup the build process with 8 jobs (threads) in parallel.
If the number is not provided, like "make -j", then there is no limit to
number jobs and it tries to run it with as many as possible.
Bests Regards,
Millad Ghane
On Thu, May 14, 2015 at 10:19 AM, Carlo Bertolli <cbertol at us.ibm.com>
wrote:
Hi
After recent commits, I am now able to compile libiomp5.so and use it in
the tests.
I noticed that the makefile in the runtime directory ultimately calls
"make ctest" in the testsuite directory.
If I do this manually "make ctest" inside testsuite after having fixed
the Makefile (again, in testuite), all selected tests are run and
verified, but at the end I see this:
cd bin/; make -j
make[1]: Entering directory
'/gsa/yktgsa-p6/05/llvm-coral-build/repos/ppc64le/libiomp/testsuite/bin'
clang -fopenmp -S -emit-llvm c/test_omp_sections_reduction.c -o
c/test_omp_sections_reduction.ll
clang -fopenmp -S -emit-llvm c/orph_ctest_omp_lock.c -o
c/orph_ctest_omp_lock.ll
clang -fopenmp -S -emit-llvm c/orph_ctest_omp_parallel_if.c -o
c/orph_ctest_omp_parallel_if.ll
....more similar commands leading to errors..
Maybe I should not use the makefile in the testsuite directory, but
apparently that is what the "make test" command does when run from the
runtime directory.
Do you have any clues about the meaning of that "make -j" command? Why is
it there and what is the intended for?
Maybe I am using a wrong repo for updating my local copy..
Thanks
-- Carlo
Inactive hide details for Sunita Chandrasekaran ---05/08/2015 03:58:04
PM---Hi Carlo If you could simply use 'make test' from oSunita
Chandrasekaran ---05/08/2015 03:58:04 PM---Hi Carlo If you could simply
use 'make test' from openmp/runtime folder, that is all
From: Sunita Chandrasekaran <sunita at cs.uh.edu>
To: Carlo Bertolli/Watson/IBM at IBMUS
Cc: "openmp-dev at dcs-maillist2.engr.illinois.edu" <
openmp-dev at dcs-maillist2.engr.illinois.edu>, Millad Ghane <
millad.mg at gmail.com>
Date: 05/08/2015 03:58 PM
Subject: Re: [Openmp-dev] testsuite script error
Sent by: sunisg123 at gmail.com
Hi Carlo
If you could simply use 'make test' from openmp/runtime folder, that is
all that is needed.
Sorry if the 2 READMEs are creating a confusion.
Please drop us a note, if you have further issues.
Thanks
Sunita
P.S: Copied is our Ph.D. student here at UH.
On Fri, May 8, 2015 at 2:27 PM, Carlo Bertolli <cbertol at us.ibm.com>
wrote:
Hi all
After fetching the latest version of the library from here:
origin http://llvm.org/git/openmp.git (fetch)
I started seeing the following error when I run "make ctest" in the
testsuite directory:
Testing for "has_openmp":
Generating sources ..........Could not open the sourcefile for the
main program ompts_standaloneProc.c at ./template_parser_c.pl line
51.
Could not open the sourcefile for the main program
ompts_standaloneProc.c at ./template_parser_c.pl line 51.
ERROR: Generation of sourcecode for the test failed.
ERROR: Generation of sourcecode for the crosstest failed.
.... failed
for all tests. This happens equally on an Intel machine and a
PCC64LE one.
What am I doing wrong?
Thanks
-- Carlo
_______________________________________________
Openmp-dev mailing list
Openmp-dev at dcs-maillist2.engr.illinois.edu
http://lists.cs.uiuc.edu/mailman/listinfo/openmp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/openmp-dev/attachments/20150514/92b389f5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/openmp-dev/attachments/20150514/92b389f5/attachment.gif>
More information about the Openmp-dev
mailing list