[LLVMdev] 2.6 pre-release1 ready for testing

[Duncan Sands]

Hi Tanya, building llvm-2.6 on x86-64 linux with gcc-4.4 I see
the following warnings (also present on mainline):

llvm-2.6/runtime/libprofile/CommonProfiling.c: In function
‘write_profiling_data’:
llvm-2.6/runtime/libprofile/CommonProfiling.c:103: warning: ignoring
return value of ‘write’, declared with attribute warn_unused_result
llvm-2.6/runtime/libprofile/CommonProfiling.c:104: warning: ignoring
return value of ‘write’, declared with attribute warn_unused_result
llvm-2.6/runtime/libprofile/CommonProfiling.c:105: warning: ignoring
return value of ‘write’, declared with attribute warn_unused_result
llvm-2.6/runtime/libprofile/CommonProfiling.c:108: warning: ignoring
return value of ‘write’, declared with attribute warn_unused_result
llvm-2.6/runtime/libprofile/CommonProfiling.c:114: warning: ignoring
return value of ‘write’, declared with attribute warn_unused_result
llvm-2.6/runtime/libprofile/CommonProfiling.c:115: warning: ignoring
return value of ‘write’, declared with attribute warn_unused_result
llvm-2.6/runtime/libprofile/CommonProfiling.c:116: warning: ignoring
return value of ‘write’, declared with attribute warn_unused_result

Results (llvm-gcc built from source):

"make check" -> 1 unexpected success
(FrontendC/2009-08-11-AsmBlocksComplexJumpTarget.c)

I think Dale fixed this on mainline.

> To test llvm-gcc:
> 1) Compile llvm from source and untar the llvm-test in the projects 
> directory (name it llvm-test or test-suite). Choose to use a 
> pre-compiled llvm-gcc or re-compile it yourself.
> 2) Run make check, report any failures (FAIL or unexpected pass). Note 
> that you need to reconfigure llvm with llvm-gcc in your path or with 
> --with-llvmgccdir
> 3) Run "make TEST=nightly report" and send me the report.nightly.txt

I've attached report.nightly.txt.

> To test clang:
> 1) Compile llvm and clang from source.
> 2) Run make check for llvm.
> 3) Run make  -C tools/clang-2.6 test VERBOSE=1 (report any failures or 
> unexpected passes)

No failures or unexpected passes.  Many warnings about aliasing problems
during the build (see PR4061).

> When reporting your results, please provide details on what platform you 
> compiled on,

x86-64 ubuntu (karmic) linux

and how
> you built LLVM (src == obj, or src != obj),clang, and/or llvm-gcc.

src != obj for all,
llvm-gcc configured with: --enable-languages=c,c++,fortran

> 
> Please COMPLETE ALL TESTING BY end of the day on Sept. 5th!

Thanks for taking care of the release!

Best wishes,

Duncan.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: report.nightly.txt
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090904/e181b403/attachment.txt>