On Wed, 2011-11-02 at 11:07 -0700, Eli Friedman wrote:> On Wed, Nov 2, 2011 at 10:38 AM, Hal Finkel <hfinkel at anl.gov> wrote: > > I'm just setting up the test suite, and I'm seeing a lot of failures > > from main() not returning int, etc. in some of the tests. Is this > > normal? > > > > For example: > > Output/2003-07-09-LoadShorts.cbe.c:117:1: error: 'main' must return > > 'int' > > unsigned int main(unsigned int llvm_cbe_argc, unsigned char > > **llvm_cbe_argv); > > Why are you trying to run the test suite using the C backend? >Good question. I just went into my build directory's projects subdirectory, checked out test-suite. Then reran the top-level configure. Then went into the projects/test-suite subdirectory and ran: make TEST=nightly report report.html (as suggested on the web page). And this is what happened. What should I be doing? Thanks again, Hal> -Eli-- Hal Finkel Postdoctoral Appointee Leadership Computing Facility Argonne National Laboratory
On Nov 2, 2011, at 11:18 AM, Hal Finkel wrote:> On Wed, 2011-11-02 at 11:07 -0700, Eli Friedman wrote: >> On Wed, Nov 2, 2011 at 10:38 AM, Hal Finkel <hfinkel at anl.gov> wrote: >>> I'm just setting up the test suite, and I'm seeing a lot of failures >>> from main() not returning int, etc. in some of the tests. Is this >>> normal? >>> >>> For example: >>> Output/2003-07-09-LoadShorts.cbe.c:117:1: error: 'main' must return >>> 'int' >>> unsigned int main(unsigned int llvm_cbe_argc, unsigned char >>> **llvm_cbe_argv); >> >> Why are you trying to run the test suite using the C backend? >> > > Good question. I just went into my build directory's projects > subdirectory, checked out test-suite. Then reran the top-level > configure. Then went into the projects/test-suite subdirectory and ran: > make TEST=nightly report report.html (as suggested on the web page). And > this is what happened. What should I be doing?Pass DISABLE_CBE=1 DISABLE_JIT=1 to the make line. More generally, you should really be using TEST=simple rather than TEST=nightly. It more accurately recreates an end-user's compiler flow, and doesn't try to test known-broken things like the CBE. --Owen
On Nov 2, 2011, at 11:31 AM, Owen Anderson wrote:> > On Nov 2, 2011, at 11:18 AM, Hal Finkel wrote: > >> On Wed, 2011-11-02 at 11:07 -0700, Eli Friedman wrote: >>> On Wed, Nov 2, 2011 at 10:38 AM, Hal Finkel <hfinkel at anl.gov> wrote: >>>> I'm just setting up the test suite, and I'm seeing a lot of failures >>>> from main() not returning int, etc. in some of the tests. Is this >>>> normal? >>>> >>>> For example: >>>> Output/2003-07-09-LoadShorts.cbe.c:117:1: error: 'main' must return >>>> 'int' >>>> unsigned int main(unsigned int llvm_cbe_argc, unsigned char >>>> **llvm_cbe_argv); >>> >>> Why are you trying to run the test suite using the C backend? >>> >> >> Good question. I just went into my build directory's projects >> subdirectory, checked out test-suite. Then reran the top-level >> configure. Then went into the projects/test-suite subdirectory and ran: >> make TEST=nightly report report.html (as suggested on the web page). And >> this is what happened. What should I be doing? > > Pass DISABLE_CBE=1 DISABLE_JIT=1 to the make line. > > More generally, you should really be using TEST=simple rather than TEST=nightly. It more accurately recreates an end-user's compiler flow, and doesn't try to test known-broken things like the CBE.All very true. It seems the web page could use an update. -j