[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Results for 3.3.2 (Debian) testsuite on i486-pc-linux-gnu

Native configuration is i486-pc-linux-gnu

		=== g++ tests ===

Running target unix
XPASS: g++.other/init5.C  Execution test

		=== g++ Summary ===

# of expected passes		8159
# of unexpected successes	1
# of expected failures		94
# of untested testcases		9
# of unsupported tests		14
/build/packages/gcc/3.3/gcc-3.3-3.3.2ds4/build/gcc/testsuite/../g++ version 3.3.2 (Debian)

		=== g77 tests ===

Running target unix

		=== g77 Summary ===

# of expected passes		1686
# of unsupported tests		8
/build/packages/gcc/3.3/gcc-3.3-3.3.2ds4/build/gcc/testsuite/../g77 version 3.3.2 (Debian)

		=== gcc tests ===

Running target unix
FAIL: gcc.dg/duff-2.c (test for excess errors)

		=== gcc Summary ===

# of expected passes		21662
# of unexpected failures	1
# of expected failures		69
# of unsupported tests		87
/build/packages/gcc/3.3/gcc-3.3-3.3.2ds4/build/gcc/xgcc version 3.3.2 (Debian)

		=== objc tests ===

Running target unix

		=== objc Summary ===

# of expected passes		1153
/build/packages/gcc/3.3/gcc-3.3-3.3.2ds4/build/gcc/xgcc version 3.3.2 (Debian)

		=== treelang tests ===

Running target unix

		=== treelang Summary ===

# of expected passes		1
		=== libjava tests ===

Running target unix
WARNING: program timed out.
FAIL: SyncTest execution - gij test
WARNING: program timed out.
FAIL: SyncTest execution - gij test

		=== libjava Summary ===

# of expected passes		2987
# of unexpected failures	2
# of expected failures		16
# of untested testcases		14

		=== libstdc++-v3 check-abi Summary ===

# of added symbols:		 0
# of missing symbols:		 0
# of incompatible symbols:	 0

using: /build/packages/gcc/3.3/gcc-3.3-3.3.2ds4/src/libstdc++-v3/config/abi/i486-linux-gnu/baseline_symbols.txt

		=== libstdc++-v3 tests ===

Running target unix
XPASS: 22_locale/collate_byname.cc execution test
XPASS: 22_locale/collate_members_char.cc execution test
XPASS: 22_locale/collate_members_wchar_t.cc execution test
XPASS: 22_locale/ctype_is_char.cc execution test
XPASS: 22_locale/ctype_is_wchar_t.cc execution test
XPASS: 22_locale/members.cc execution test
XPASS: 22_locale/messages_byname.cc execution test
XPASS: 22_locale/messages_members_char.cc execution test
XPASS: 22_locale/moneypunct_byname.cc execution test
XPASS: 22_locale/moneypunct_members_char.cc execution test
XPASS: 22_locale/moneypunct_members_wchar_t.cc execution test
XPASS: 22_locale/numpunct_byname.cc execution test
XPASS: 22_locale/numpunct_members_char.cc execution test
XPASS: 22_locale/numpunct_members_wchar_t.cc execution test

		=== libstdc++-v3 Summary ===

# of expected passes		453
# of unexpected successes	14
# of expected failures		14

Compiler version: 3.3.2 (Debian) 
Platform: i486-pc-linux-gnu
configure flags: --host=i486-linux -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc

Build Dependencies:
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
ii  binutils  The GNU assembler, linker and binary utiliti
ii  libc6-dev      2.3.2-9        GNU C Library: Development Libraries and Hea

Patches that Debian applied in this version:

  versioned gcc names

  Add "(Debian)" to the gcc version string

  Build and install libstdc++_pic.a library.

  link local libstdc++ documentation to local source-level documentation 

  Use sensible-editor instead of vi as fallback editor

  2003-03-10  Andreas Schwab  <schwab at suse dot de>
  With the introduction of multi-os-directory the libdir specification in
  *.la files have /. appended to \$(libdir).  This confuses libtool when it
  tries to find out whether to add -rpath, because it only matches literally
  against sys_lib_dlsearch_path members.  Tested on i386-linux.

  Fix #207915 (PR11716).
  Make GCC think that the maximum length of a short branch is
  64K instead of 128K.  It's a big hammer, but it works.

  2003-05-16  Jakub Jelinek  <jakub@redhat.com>
  	* config/ia64/unwind-ia64.c (uw_update_reg_address): Handle
  	.save XX, r0.

  Update from the gcc-3_3-branch:
  2003-10-23  Jason Merrill  <jason@redhat.com>
  PR c++/12726
  * tree.c (build_target_expr_with_type): Don't call force_rvalue

  2003-10-20  Falk Hueffner  <falk@debian.org>
  	PR target/12654
  	* config/alpha/alpha.c (alpha_emit_conditional_branch): Don't do
  	comparison against constant by adjusting the argument except for
  	EQ and NE.

  add libstdc++-v3's check summary to the test summary

  versioned gcj info names

  don't define runtime link path for java binaries and libraries

  Allows libffi to be installed

  Do not build libffi with debug information, although configuring
  with --enable-debug

  build protoize/unprotoize by default

  Find gc.h header in /usr/include/gc for --enable-objc-gc enabled builds.

  versioned g77 names

  Install treelang info pages under versioned name

  use gcc-3.3 instead of gcc and gnatXXX-3.15 instead of gnatXXX
  as the command names.

  update the gpc diffs to recent gcc sources

  The gpc patch from the gpc tarball.

  gpc-20030830 have a memory management bug which is probably 
  responsible for crashes reported by Adriaan van Os and 
  Maurice Lombardi. Mainly builds with gcc-3.3.x are affected
  (I do not know if it is possible to trigger the bug with 
  earlier gcc version). The patch below fixes the problem:

  versioned gpc names

  generate code for architecture i486, tuned for i686 by default.

  <compiler> --help gives hint to /usr/share/doc/debian/bug-reporting.txt

  autoreconf several directories for proper mipsen libtool support

Counting all warnings,
there are 333 warnings in stage3 of this bootstrap.

Number of warnings per file:
    225 SYSCALLS.c
     49 parse.c
      6 ./ffe.texi
      5 gcc/treelang/parse.c
      4 gcc/p/statements.c
      4 gcc/p/lang-specs.h
      4 ./intdoc.texi
      3 gcc/tlink.c
      3 gcc/p/gpc.c
      3 gcc/gcc.c
      3 /usr/share/bison/bison.simple
      2 insn-conditions.c
      2 gcc/p/rts/endian.pas
      2 gcc/objc/lang-specs.h
      2 gcc/function.c
      2 gcc/f/sta.c
      2 gcc/crtstuff.c
      1 libiberty/choose-temp.c
      1 gt-ada-utils.h
      1 gt-ada-decl.h
      1 gcc/unwind-pe.h
      1 gcc/p/objects.c
      1 gcc/p/gpc-lex.c
      1 gcc/java/jvspec.c
      1 gcc/emit-rtl.c
      1 gcc/config/i386/i386.c
      1 gcc/collect2.c
      1 gcc/ada/tracebak.c
      1 ada/b_gnatb.c

Number of warning types:
    223 function declaration isn't a prototype
     55 traditional C rejects ISO C style function definitions
     13 string length `???' is greater than the length `???' ISO C89 compilers are required to support
      6 undefined flag: srcdir.
      5 comparison of unsigned expression < 0 is always false
      3 label `???' defined but not used
      3 comparison between signed and unsigned
      3 assignment makes pointer from integer without a cast
      2 unlikely character ) in @var.
      2 unlikely character ( in @var.
      2 traditional C rejects string concatenation
      2 statement with no effect
      2 signed and unsigned type in conditional expression
      2 passing arg ??? of `???' discards qualifiers from pointer target type
      2 dereferencing type-punned pointer will break strict-aliasing rules
      2 conflicting types for built-in function `???'
      1 unused variable `???'
      1 unused parameter `???'
      1 the use of `???' is dangerous, better use `???'
      1 initialization makes pointer from integer without a cast
      1 implicit declaration of function `???'
      1 `???' defined but not used

Reply to: