Bug#433391: gij-4.1: Runs out of memory

2007-07-24 Thread Matthias Klose
severity 433391 grave
clone 433391 -1
reassign -1 glibc
block 433391 by -1
thanks

Building gcj or gcc-snapshot on a system downgraded to glibc-2.5
doesn't show the testsuite failures in libjava.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Processed: Re: gij-4.1: Runs out of memory

2007-07-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> severity 433391 grave
Bug#433391: gij-4.1: Runs out of memory
Severity set to `grave' from `serious'

> clone 433391 -1
Bug#433391: gij-4.1: Runs out of memory
Bug 433391 cloned as bug 434484.

> reassign -1 glibc
Bug#434484: gij-4.1: Runs out of memory
Bug reassigned from package `gij-4.1' to `glibc'.

> block 433391 by -1
Bug#434484: gij-4.1: Runs out of memory
Bug#433391: gij-4.1: Runs out of memory
Was not blocked by any bugs.
Blocking bugs of 433391 added: 434484

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#423383: marked as done (gcj-4.2: compilation fails; libgcj.spec not found)

2007-07-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Jul 2007 09:05:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#423383: gcj-4.2: compilation fails; libgcj.spec not found
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: gcj-4.2
Version: 4.2-20070405-1
Severity: normal



Trying to compile a very simple test program fails:

   $ LANG=C gcj-4.2 -c Test.java
   gcj-4.2: libgcj.spec: No such file or directory

Here's the simple test prog ftw:

   public class Test
   {
   public static void main(String[] args)
   {
   System.out.println("hello world");
   }
   }


Thanks,

-miles


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gcj-4.2 depends on:
ii  ecj 3.2.2-2  standalone version of the Eclipse 
ii  gcc-4.2 4.2-20070405-1   The GNU C compiler
ii  gcj-4.2-base4.2-20070405-1   The GNU Compiler Collection (gcj b
ii  gij-4.2 4.2-20070405-1   The GNU Java bytecode interpreter
ii  java-common 0.25 Base of all Java packages
ii  libc6   2.5-7GNU C Library: Shared libraries
ii  libc6-dev   2.5-7GNU C Library: Development Librari
ii  libgcc1 1:4.2-20070405-1 GCC support library
ii  libgcj-bc   4.1.2-2  Link time only library for use wit
ii  libgcj8-dev 4.2-20070405-1   Java development headers and stati
ii  libgcj8-jar 4.2-20070405-1   Java runtime library for use with 
ii  zlib1g  1:1.2.3-13   compression library - runtime

Versions of packages gcj-4.2 recommends:
ii  ecj-gcj   3.2.2-2standalone version of the Eclipse 
ii  fastjar   2:0.95-1   Jar creation utility

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 4.2.1-0

unreproducible.

Miles Bader writes:
> Package: gcj-4.2
> Version: 4.2-20070405-1
> Severity: normal
> 
> 
> 
> Trying to compile a very simple test program fails:
> 
>$ LANG=C gcj-4.2 -c Test.java
>gcj-4.2: libgcj.spec: No such file or directory
> 
> Here's the simple test prog ftw:
> 
>public class Test
>{
>public static void main(String[] args)
>{
>  System.out.println("hello world");
>}
>}
--- End Message ---


[Bug java/32862] bug in EnumMap implementation

2007-07-24 Thread cvs-commit at developer dot classpath dot org


--- Comment #2 from cvs-commit at developer dot classpath dot org  
2007-07-24 15:27 ---
Subject: Bug 32862

CVSROOT:/cvsroot/classpath
Module name:classpath
Changes by: Tom Tromey  07/07/24 15:26:36

Modified files:
.  : ChangeLog 
java/util  : EnumMap.java 

Log message:
PR java/32862:
* java/util/EnumMap.java (get): Special case emptySlot.
(clone): Rewrote.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/classpath/ChangeLog?cvsroot=classpath&r1=1.9354&r2=1.9355
http://cvs.savannah.gnu.org/viewcvs/classpath/java/util/EnumMap.java?cvsroot=classpath&r1=1.4&r2=1.5


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32862

--- You are receiving this mail because: ---
You reported the bug, or are watching the reporter.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#431454: marked as done (gcc-snapshot - FTBFS: gcj-4.1: command not found)

2007-07-24 Thread Debian Bug Tracking System
Your message dated Wed, 25 Jul 2007 01:24:58 +0200
with message-id <[EMAIL PROTECTED]>
and subject line gcc-snapshot - FTBFS: gcj-4.1: command not found
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: gcc-snapshot
Version: 20070630-1
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of gcc-snapshot_20070630-1 on lxdebian.bfinv.de by 
> sbuild/s390 98
[...]
> /bin/bash: line 14: gcj-4.1: command not found
> make[1]: *** [stamps/05-build-stamp] Error 127
> make[1]: Leaving directory `/build/buildd/gcc-snapshot-20070630'
> make: *** [stamps/05-build-stamp] Error 2
> **
> Build finished at 20070702-1845
> FAILED [dpkg-buildpackage died]

--- End Message ---
--- Begin Message ---
Version: 20070720-1

built: 
http://buildd.debian.org/fetch.cgi?&pkg=gcc-snapshot&ver=20070720-1&arch=s390&stamp=1185044895&file=log
--- End Message ---


Results for 4.1.3 20070718 (prerelease) (Debian 4.1.2-14) testsuite on arm-unknown-linux-gnu

2007-07-24 Thread Matthias Klose
LAST_UPDATED: Wed Jul 18 17:04:05 UTC 2007 (revision 126723)

Native configuration is arm-unknown-linux-gnu

=== libmudflap tests ===


Running target unix

=== libmudflap Summary ===

# of expected passes1799
=== libstdc++ tests ===


Running target unix
XPASS: 26_numerics/cmath/c99_classification_macros_c.cc (test for excess errors)
FAIL: 
tr1/4_metaprogramming/other_transformations/aligned_storage/aligned_storage.cc 
execution test
FAIL: tr1/4_metaprogramming/type_properties/is_empty/is_empty.cc execution test
FAIL: tr1/4_metaprogramming/type_properties/is_polymorphic/is_polymorphic.cc 
execution test

=== libstdc++ Summary ===

# of expected passes3394
# of unexpected failures3
# of unexpected successes   1
# of expected failures  12
# of unsupported tests  324
Target: arm-linux-gnu
gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)

=== g++ tests ===


Running target unix
FAIL: tmpdir-g++.dg-struct-layout-1/t026 cp_compat_x_tst.o-cp_compat_y_tst.o 
execute 
XPASS: g++.dg/other/packed1.C execution test
XPASS: g++.dg/tree-ssa/pr14814.C scan-tree-dump-times &this 0
FAIL: g++.old-deja/g++.eh/badalloc1.C execution test
XPASS: g++.old-deja/g++.other/init5.C execution test

=== g++ Summary ===

# of expected passes12393
# of unexpected failures2
# of unexpected successes   3
# of expected failures  66
# of unsupported tests  108
/build/buildd/gcc-4.1-4.1.2/build/gcc/testsuite/g++/../../g++  version 4.1.3 
20070718 (prerelease) (Debian 4.1.2-14)

=== gcc tests ===


Running target unix
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c  -O1  (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c  -O2  (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c  -O3 -fomit-frame-pointer  (test for 
excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c  -O3 -g  (test for excess errors)
WARNING: program timed out.
FAIL: gcc.c-torture/compile/20001226-1.c  -Os  (test for excess errors)
FAIL: gcc.c-torture/execute/20050121-1.c compilation,  -O0  (internal compiler 
error)
UNRESOLVED: gcc.c-torture/execute/20050121-1.c execution,  -O0 
FAIL: gcc.dg/compat/scalar-return-4 c_compat_y_tst.o compile,  (internal 
compiler error)
UNRESOLVED: gcc.dg/compat/scalar-return-4 c_compat_x_tst.o-c_compat_y_tst.o 
link 
UNRESOLVED: gcc.dg/compat/scalar-return-4 c_compat_x_tst.o-c_compat_y_tst.o 
execute 
FAIL: gcc.dg/arm-mmx-1.c (test for excess errors)
ERROR: gcc.dg/arm-mmx-1.c: error executing dg-final: couldn't open 
"arm-mmx-1.s": no such file or directory
UNRESOLVED: gcc.dg/arm-mmx-1.c: error executing dg-final: couldn't open 
"arm-mmx-1.s": no such file or directory

=== gcc Summary ===

# of expected passes38046
# of unexpected failures8
# of expected failures  77
# of unresolved testcases   4
# of untested testcases 28
# of unsupported tests  312
/build/buildd/gcc-4.1-4.1.2/build/gcc/xgcc  version 4.1.3 20070718 (prerelease) 
(Debian 4.1.2-14)

=== gfortran tests ===


Running target unix
FAIL: gfortran.dg/common_5.f  -O   (test for warnings, line 6)
XPASS: gfortran.dg/csqrt_2.f  -O0  execution test
XPASS: gfortran.dg/csqrt_2.f  -O1  execution test
XPASS: gfortran.dg/csqrt_2.f  -O2  execution test
XPASS: gfortran.dg/csqrt_2.f  -O3 -fomit-frame-pointer  execution test
XPASS: gfortran.dg/csqrt_2.f  -O3 -fomit-frame-pointer -funroll-loops  
execution test
XPASS: gfortran.dg/csqrt_2.f  -O3 -fomit-frame-pointer -funroll-all-loops 
-finline-functions  execution test
XPASS: gfortran.dg/csqrt_2.f  -O3 -g  execution test
XPASS: gfortran.dg/csqrt_2.f  -Os  execution test
FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 execution,  -O0 
FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 execution,  -O1 
FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 execution,  -O2 
FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 execution,  -O3 
-fomit-frame-pointer 
FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 execution,  -O3 
-fomit-frame-pointer -funroll-loops 
FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 execution,  -O3 
-fomit-frame-pointer -funroll-all-loops -finline-functions 
FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 execution,  -O3 
-g 
FAIL: gfortran.fortran-torture/execute/intrinsic_rrspacing.f90 execution,  -Os 
FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90 execution,  
-O0 
FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90 execution,  
-O1 
FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.f90 execution,  
-O2 
FAIL: gfortran.fortran-torture/execute/intrinsic_set_exponent.

Results for 4.2.1 (Debian 4.2.1-0) testsuite on arm-unknown-linux-gnu

2007-07-24 Thread Matthias Klose
LAST_UPDATED: Thu Jul 19 15:44:56 UTC 2007 (revision 126787)

Native configuration is arm-unknown-linux-gnu

=== libffi tests ===


Running target unix
FAIL: libffi.call/cls_1_1byte.c -O0 -W -Wall execution test
FAIL: libffi.call/cls_5_1_byte.c -O0 -W -Wall output pattern test, is 127 120 1 
3 4 3 4 28 64 56: 130 124 29 67 60
FAIL: libffi.call/cls_5byte.c -O0 -W -Wall output pattern test, is 127 120 1 
128 9 68: 255 129 69
FAIL: libffi.call/cls_6_1_byte.c -O0 -W -Wall output pattern test, is 127 120 1 
3 4 5 9 3 4 5 48 94: 136 123 5 8 52 99
FAIL: libffi.call/cls_6byte.c -O0 -W -Wall output pattern test, is 127 120 1 
128 128 32521 64 190: 255 32641 65 62
FAIL: libffi.call/cls_7_1_byte.c -O0 -W -Wall output pattern test, is 127 120 1 
3 4 5 6 128 9 3 4 5 6 163: 255 129 4 7 9 11 169
FAIL: libffi.call/cls_align_sint16.c -O0 -W -Wall output pattern test, is 12 
4951 127 104 13 52: 116 4964 179
FAIL: libffi.call/cls_align_uint16.c -O0 -W -Wall output pattern test, is 12 
4951 127 104 13 52: 116 4964 179
FAIL: libffi.call/struct3.c -O0 -W -Wall execution test
FAIL: libffi.call/cls_1_1byte.c -O2 execution test
FAIL: libffi.call/cls_5_1_byte.c -O2 output pattern test, is 127 120 1 3 4 3 4 
0 0 40: 130 124 1 3 44
FAIL: libffi.call/cls_5byte.c -O2 output pattern test, is 127 120 1 128 9 48: 
255 129 49
FAIL: libffi.call/cls_6_1_byte.c -O2 output pattern test, is 127 120 1 3 4 5 9 
3 4 5 32 238: 136 123 5 8 36 243
FAIL: libffi.call/cls_6byte.c -O2 output pattern test, is 127 120 1 128 128 
32521 44 190: 255 32641 45 62
FAIL: libffi.call/cls_7_1_byte.c -O2 output pattern test, is 127 120 1 3 4 5 6 
128 9 3 4 5 6 243: 255 129 4 7 9 11 249
FAIL: libffi.call/cls_align_sint16.c -O2 output pattern test, is 12 4951 127 
104 13 36: 116 4964 163
FAIL: libffi.call/cls_align_uint16.c -O2 output pattern test, is 12 4951 127 
104 13 36: 116 4964 163
FAIL: libffi.call/struct3.c -O2 execution test
FAIL: libffi.call/cls_1_1byte.c -O3 execution test
FAIL: libffi.call/cls_5_1_byte.c -O3 output pattern test, is 127 120 1 3 4 3 4 
0 0 40: 130 124 1 3 44
FAIL: libffi.call/cls_5byte.c -O3 output pattern test, is 127 120 1 128 9 48: 
255 129 49
FAIL: libffi.call/cls_6_1_byte.c -O3 output pattern test, is 127 120 1 3 4 5 9 
3 4 5 32 30: 136 123 5 8 36 35
FAIL: libffi.call/cls_6byte.c -O3 output pattern test, is 127 120 1 128 128 
32521 44 158: 255 32641 45 30
FAIL: libffi.call/cls_7_1_byte.c -O3 output pattern test, is 127 120 1 3 4 5 6 
128 9 3 4 5 6 155: 255 129 4 7 9 11 161
FAIL: libffi.call/cls_align_sint16.c -O3 output pattern test, is 12 4951 127 
104 13 36: 116 4964 163
FAIL: libffi.call/cls_align_uint16.c -O3 output pattern test, is 12 4951 127 
104 13 36: 116 4964 163
FAIL: libffi.call/struct3.c -O3 execution test
FAIL: libffi.call/cls_1_1byte.c -Os execution test
FAIL: libffi.call/cls_5_1_byte.c -Os output pattern test, is 127 120 1 3 4 3 4 
0 0 44: 130 124 1 3 48
FAIL: libffi.call/cls_5byte.c -Os output pattern test, is 127 120 1 128 9 52: 
255 129 53
FAIL: libffi.call/cls_6_1_byte.c -Os output pattern test, is 127 120 1 3 4 5 9 
3 4 5 36 78: 136 123 5 8 40 83
FAIL: libffi.call/cls_6byte.c -Os output pattern test, is 127 120 1 128 128 
32521 48 94: 255 32641 49 222
FAIL: libffi.call/cls_7_1_byte.c -Os output pattern test, is 127 120 1 3 4 5 6 
128 9 3 4 5 6 221: 255 129 4 7 9 11 227
FAIL: libffi.call/cls_align_sint16.c -Os output pattern test, is 12 4951 127 
104 13 36: 116 4964 163
FAIL: libffi.call/cls_align_uint16.c -Os output pattern test, is 12 4951 127 
104 13 36: 116 4964 163
FAIL: libffi.call/struct3.c -Os execution test

=== libffi Summary ===

# of expected passes1056
# of unexpected failures36
# of unsupported tests  8
=== libgomp tests ===


Running target unix

=== libgomp Summary ===

# of expected passes1560
# of unsupported tests  7
=== libmudflap tests ===


Running target unix

=== libmudflap Summary ===

# of expected passes1814
=== libstdc++ tests ===


Running target unix
FAIL: 19_diagnostics/23591_thread-1.c execution test
FAIL: 22_locale/ctype/cons/char/1.cc execution test
FAIL: 23_containers/deque/modifiers/swap/3.cc execution test
FAIL: 23_containers/list/modifiers/swap/3.cc execution test
FAIL: 23_containers/map/modifiers/swap/3.cc execution test
FAIL: 23_containers/multimap/modifiers/swap/3.cc execution test
FAIL: 23_containers/multiset/modifiers/swap/3.cc execution test
FAIL: 23_containers/set/modifiers/swap/3.cc execution test
FAIL: 23_containers/vector/bool/modifiers/swap/2.cc execution test
FAIL: 23_containers/vector/modifiers/swap/3.cc execution test
XPASS: 26_numerics/cmath/c99_classification_macros_c.cc (test for excess errors)
WARNING: program timed out.
FAIL: ext/pb_ds/regression/hash_data_map_rand.cc (test for excess errors)
UNRESOLVED: ext/pb_ds/regression/hash_data_map_rand.cc compilation failed to 
produce executable
WARN

Results for 4.2.1 (Debian 4.2.1-0) libjava testsuite on alpha-unknown-linux-gnu

2007-07-24 Thread Matthias Klose
LAST_UPDATED: Thu Jul 19 15:44:56 UTC 2007 (revision 126787)

Native configuration is alpha-unknown-linux-gnu

=== libjava tests ===


Running target unix
WARNING: program timed out.
FAIL: pr11951 run
FAIL: natgetargssize.cc compilation
FAIL: natgetlocalvartable.cc compilation
FAIL: natgetstacktrace.cc compilation
FAIL: natevents.cc compilation
FAIL: natgetallthreads.cc compilation
FAIL: natgeterrorname.cc compilation
FAIL: natgetmethodname.cc compilation
WARNING: program timed out.
FAIL: PR26858 -O3 -findirect-dispatch compilation from source
FAIL: initexc execution - source compiled test
FAIL: initexc -findirect-dispatch execution - source compiled test
FAIL: initexc -O3 execution - source compiled test
FAIL: initexc -O3 -findirect-dispatch execution - source compiled test
WARNING: program timed out.
FAIL: invokethrow execution - source compiled test
FAIL: invokethrow -findirect-dispatch output - source compiled test
WARNING: program timed out.
FAIL: invokethrow -O3 execution - source compiled test
FAIL: invokethrow -O3 -findirect-dispatch output - source compiled test

=== libjava Summary ===

# of expected passes2508
# of unexpected failures17
# of untested testcases 9
Target: alpha-linux-gnu
gcc version 4.2.1 (Debian 4.2.1-0)

Compiler version: 4.2.1 (Debian 4.2.1-0) libjava 
Platform: alpha-unknown-linux-gnu
configure flags: -v --prefix=/usr --enable-shared --with-system-zlib 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--enable-nls --with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2 
--enable-clocale=gnu --enable-java-awt=gtk --enable-gtk-cairo --enable-plugin 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.2-1.5.0.0/jre 
--with-ecj-jar=/usr/share/java/ecj.jar --disable-libmudflap --disable-libssp 
--disable-werror --with-long-double-128 --enable-checking=release 
--build=alpha-linux-gnu --host=alpha-linux-gnu --target=alpha-linux-gnu 
--enable-languages=c,c++,java
BOOT_CFLAGS=-O2


Build Dependencies:
Desired=Unknown/Install/Remove/Purge/Hold
| 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   2.17cvs20070718-1 The GNU assembler, linker and binary 
utilities
ii  libc6.12.6-2 GNU C Library: Shared libraries


Patches that Debian applied in this version:

rename-info-files:
  Allow transformations on info file names. Reference the
  transformed info file names in the texinfo files.

gcc-version:
  Add package identification to the gcc version string

gcc-textdomain:
  Set gettext's domain and textdomain to the versioned package name.

gcc-driver-extra-langs:
  Add options and specs for languages that are not built from a source
  (but built from separate sources).

gcc-hash-style-both:
  Link using --hash-style=both (alpha, amd64, ia64, i386, powerpc, ppc64, s390, 
sparc)

libstdc++-pic:
  Build and install libstdc++_pic.a library.

libstdc++-doclink:
  adjust hrefs to point to the local documentation

gccbug:
  Use sensible-editor instead of vi as fallback editor

gccbug-posix:
  Make gccbug POSIX compliant (patch by David Weinehall)
  http://www.opengroup.org/onlinepubs/009695399/utilities/test.html

libstdc++-doxygen:
  libstdc++ doxygen docs: Set SHORT_NAMES to YES

libjava-stacktrace:
  libgcj: Lookup source file name and line number in separated
  debug files found in /usr/lib/debug

libjava-subdir:
  - Set the libjava sublibdir to /usr/lib/gcj-4.2
  - Set the default libgcj database dir to /var/lib/gcj-4.2

libjava-lib32subdir:
  - When running the i386 binaries on amd64, look in /usr/lib32/gcj-x-y

libjava-jnipath:
  - Add /usr/lib/jni to java.library.path.
  - When running the i386 binaries on amd64, look in
  - /usr/lib32/gcj-x.y and /usr/lib32/jni instead.

libjava-lib32-properties:
  - When running the i386 binaries on amd64, adjust the properties
  java.home, gnu.classpath.home.url, sun.boot.class.path,
  gnu.gcj.precompiled.db.path.

libjava-sjlj:
  Don't try to use _Unwind_Backtrace on SJLJ targets.
  See bug #387875, #388505, GCC PR 29206.

libjava-rpath:
  - Link ecjx and gij with -rpath \$(dbexecdir)

libjava-examples:
  Fix build for libjava/classpath/examples

libffi-configure:
  Add --enable-libffi option to toplevel configure script

pr20218:
  Backport from mainline for PR middle-end/17982, PR middle-end/20218.

pr20218-mips:
  Backport from mainline for PR middle-end/20218, mips part.

pr28102:
  Apply proposed fix for PR target/28102.

pr31868:
  Backport from mainline for PR target/31868

pr32723:
  Proposed patch for PR tree-optimization/32723

alpha-no-ev4-directive:

boehm-gc-nocheck:
  Disable running the boehm-gc testsuite. Hangs the buildd at least on hppa.

note-gnu-stack:
  Add .note.GNU-stack sec

Results for 4.2.1 (Debian 4.2.1-0) libjava testsuite on s390-ibm-linux-gnu

2007-07-24 Thread Matthias Klose
LAST_UPDATED: Thu Jul 19 15:44:56 UTC 2007 (revision 126787)

Target: s390-linux-gnu
gcc version 4.2.1 (Debian 4.2.1-0)
Native configuration is s390-ibm-linux-gnu

=== libjava tests ===


Running target unix

=== libjava Summary for unix ===

# of expected passes2546

Running target unix/-fstack-protector

=== libjava Summary for unix/-fstack-protector ===

# of expected passes2546

Running target unix/-m64
FAIL: linking PR9577
FAIL: linking longfield
FAIL: linking shortfield
FAIL: linking TestClosureGC
FAIL: linking simple
FAIL: linking PR15133
FAIL: linking PR18116
FAIL: linking PR28178
FAIL: linking bytebuffer
FAIL: linking calls
FAIL: linking cxxtest
FAIL: linking directbuffer
FAIL: linking field
FAIL: linking final_method
FAIL: linking findclass
FAIL: linking findclass2
FAIL: linking iface
FAIL: linking init
FAIL: linking invoke
FAIL: linking jniutf
FAIL: linking martin
FAIL: linking noclass
FAIL: linking overload
FAIL: linking pr11951
FAIL: linking pr18278
FAIL: linking pr23739
FAIL: linking register
FAIL: linking register2
FAIL: linking simple_int
FAIL: linking throwit
FAIL: linking virtual
FAIL: linking events
FAIL: linking getallthreads
FAIL: linking geterrorname
FAIL: linking getmethodname
FAIL: ArrayStore compilation from source
FAIL: ArrayStore -findirect-dispatch compilation from source
FAIL: ArrayStore -O3 compilation from source
FAIL: ArrayStore -O3 -findirect-dispatch compilation from source
FAIL: ArrayStore2 compilation from source
FAIL: ArrayStore2 -findirect-dispatch compilation from source
FAIL: ArrayStore2 -O3 compilation from source
FAIL: ArrayStore2 -O3 -findirect-dispatch compilation from source
FAIL: Array_1 compilation from source
FAIL: Array_1 -findirect-dispatch compilation from source
FAIL: Array_1 -O3 compilation from source
FAIL: Array_1 -O3 -findirect-dispatch compilation from source
FAIL: Array_2 compilation from source
FAIL: Array_2 -findirect-dispatch compilation from source
FAIL: Array_2 -O3 compilation from source
FAIL: Array_2 -O3 -findirect-dispatch compilation from source
FAIL: Array_3 compilation from source
FAIL: Array_3 -findirect-dispatch compilation from source
FAIL: Array_3 -O3 compilation from source
FAIL: Array_3 -O3 -findirect-dispatch compilation from source
FAIL: Class_1 compilation from source
FAIL: Class_1 -findirect-dispatch compilation from source
FAIL: Class_1 -O3 compilation from source
FAIL: Class_1 -O3 -findirect-dispatch compilation from source
FAIL: CompareNaN compilation from source
FAIL: CompareNaN -findirect-dispatch compilation from source
FAIL: CompareNaN -O3 compilation from source
FAIL: CompareNaN -O3 -findirect-dispatch compilation from source
FAIL: Divide_1 compilation from source
FAIL: Divide_1 -findirect-dispatch compilation from source
FAIL: Divide_1 -O3 compilation from source
FAIL: Divide_1 -O3 -findirect-dispatch compilation from source
FAIL: Divide_2 compilation from source
FAIL: Divide_2 -findirect-dispatch compilation from source
FAIL: Divide_2 -O3 compilation from source
FAIL: Divide_2 -O3 -findirect-dispatch compilation from source
FAIL: EvaluationOrder compilation from source
FAIL: EvaluationOrder -findirect-dispatch compilation from source
FAIL: EvaluationOrder -O3 compilation from source
FAIL: EvaluationOrder -O3 -findirect-dispatch compilation from source
FAIL: ExtraClassLoader compilation from source
FAIL: ExtraClassLoader -findirect-dispatch compilation from source
FAIL: ExtraClassLoader -O3 compilation from source
FAIL: ExtraClassLoader -O3 -findirect-dispatch compilation from source
FAIL: FileHandleGcTest compilation from source
FAIL: FileHandleGcTest -findirect-dispatch compilation from source
FAIL: FileHandleGcTest -O3 compilation from source
FAIL: FileHandleGcTest -O3 -findirect-dispatch compilation from source
FAIL: Final compilation from source
FAIL: Final -findirect-dispatch compilation from source
FAIL: Final -O3 compilation from source
FAIL: Final -O3 -findirect-dispatch compilation from source
FAIL: Float_1 compilation from source
FAIL: Float_1 -findirect-dispatch compilation from source
FAIL: Float_1 -O3 compilation from source
FAIL: Float_1 -O3 -findirect-dispatch compilation from source
FAIL: Float_2 compilation from source
FAIL: Float_2 -findirect-dispatch compilation from source
FAIL: Float_2 -O3 compilation from source
FAIL: Float_2 -O3 -findirect-dispatch compilation from source
FAIL: G19990301_01 compilation from source
FAIL: G19990301_01 -findirect-dispatch compilation from source
FAIL: G19990301_01 -O3 compilation from source
FAIL: G19990301_01 -O3 -findirect-dispatch compilation from source
FAIL: G19990302_02 compilation from source
FAIL: G19990302_02 -findirect-dispatch compilation from source
FAIL: G19990302_02 -O3 compilation from source
FAIL: G19990302_02 -O3 -findirect-dispatch compilation from source
FAIL: G19990303_01 compilation from source
FAIL: G19990303_01 -findirect-dispatch compilation from source
FAIL: G19990303_01

Bug#433172: gcc-4.2: probably different issue

2007-07-24 Thread Simon Richter
Package: gcc-4.2
Version: 4.2.1-0
Followup-For: Bug #433172

Hi,

while the patch indeed hides the problem, the real issue seems to be
deeper. Being listed in ssp_no_archs has an effect on the build process
of the bootstrap(!) compiler; my guess is that ARM is listed there
because building a cross compiler using a host compiler that doesn't
know about SSP will fail unless you claim that the target isn't capable
of SSP, which will remove the -fno-stack-protector from the
STAGE1_CFLAGS and BOOT_CFLAGS.

I'm not entirely sure that there is any need to compile the bootstrap
compiler without SSP if the system default compiler uses it by default,
as the bootstrap compiler is never used after the bootstrap process
anyway.

In fact, I think the main reason the list of architectures is dependent
on DEB_CROSS is that the person who made the initial change wanted to do
a minimally invasive patch that only affected cross builds; however the
end result is suboptimal as

 a) native builds (i386 -> i386) using older compilers fail, because the
(old) system compiler is given the -fno-stack-protector flag, and
 b) the resulting cross compiler will not use stack protector, even if
it would be supported on that architecture.

Unconditionally removing these flags from the STAGE1 and BOOT CFLAGS
seems not to have the desired effect, as the fixincludes binary built by
the stage1 compiler then uses stack protector (as it seems to be
default when compiling on an Ubuntu system), but fixincludes does not
link libssp. This paragraph should be taken with a grain of salt,
however, as this happened in an Ubuntu Dapper chroot running on a Debian
sid box, so the build might just have expected SSP support from the C
library (but that may be another bug in itself).

   Simon

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.21-2-amd64 (SMP w/1 CPU core)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



[Bug c++/32888] Declared long long double has wrong type

2007-07-24 Thread pinskia at gcc dot gnu dot org


--- Comment #1 from pinskia at gcc dot gnu dot org  2007-07-25 02:35 ---


*** This bug has been marked as a duplicate of 6634 ***


-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||DUPLICATE


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32888

--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



[Bug c++/6634] wrong parsing of "long long double"

2007-07-24 Thread pinskia at gcc dot gnu dot org


--- Comment #13 from pinskia at gcc dot gnu dot org  2007-07-25 02:35 
---
*** Bug 32888 has been marked as a duplicate of this bug. ***


-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||igodard at pacbell dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6634

--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who is.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]