test suite and int main

Project Infrastructure LLVM Dev List Archives
#1

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);
^
Output/2003-07-09-LoadShorts.cbe.c:117:14: error: first parameter of
'main' (argument count) must be of type 'int'
unsigned int main(unsigned int llvm_cbe_argc, unsigned char
**llvm_cbe_argv);
             ^
Output/2003-07-09-LoadShorts.cbe.c:117:14: error: second parameter of
'main' (argument array) must be of type 'char **'

Thanks again,
Hal

#2

Why are you trying to run the test suite using the C backend?

-Eli

#3

> 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

#4

Hi Hal,

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?

the C backend is totally broken. You can just ignore it.

Ciao, Duncan.

#5

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

#6

All very true. It seems the web page could use an update.

-j