Bug#288152: marked as done (gcc-snapshot: FTBFS on amd64.)

2005-02-13 Thread Debian Bug Tracking System 
Your message dated Sun, 13 Feb 2005 10:45:23 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-snapshot_20050212-1
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)

--
Received: (at submit) by bugs.debian.org; 1 Jan 2005 22:56:30 +
>From [EMAIL PROTECTED] Sat Jan 01 14:56:30 2005
Return-path: <[EMAIL PROTECTED]>
Received: from asia.telenet-ops.be [195.130.132.59] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CksAg-0002tR-00; Sat, 01 Jan 2005 14:56:30 -0800
Received: from localhost (localhost.localdomain [127.0.0.1])
by asia.telenet-ops.be (Postfix) with SMTP id ADC1022404E
for <[EMAIL PROTECTED]>; Sat,  1 Jan 2005 23:56:28 +0100 (MET)
Received: from kabel.telenet.be (D5775FD9.kabel.telenet.be [213.119.95.217])
by asia.telenet-ops.be (Postfix) with ESMTP id 9F0BD2240D5
for <[EMAIL PROTECTED]>; Sat,  1 Jan 2005 23:56:28 +0100 (MET)
Received: by kabel.telenet.be (Postfix, from userid 501)
id 5CD2E26136; Sat, 01 Jan 2005 23:56:26 +0100 (CET)
Date: Sat, 1 Jan 2005 23:56:26 +0100
From: Kurt Roeckx <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: gcc-snapshot: FTBFS on amd64.
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: gcc-snapshot
Version: 20041231-1

Hi,

The gcc-snapshot currently fails to build on amd64.  One of the
reasons is that it's building a biarch compiler and not build
depending on the ia32-libs.

Could you do the same for gcc-snapshot as for gcc-3.4?


Kurt


---
Received: (at 288152-done) by bugs.debian.org; 13 Feb 2005 09:45:28 +
>From [EMAIL PROTECTED] Sun Feb 13 01:45:28 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D0GJk-0007vI-00; Sun, 13 Feb 2005 01:45:28 -0800
Received: from mailhost.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.17.13])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id KAA17815;
Sun, 13 Feb 2005 10:45:26 +0100 (MET)
Received: from localhost (localhost [127.0.0.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 7E4C3F215;
Sun, 13 Feb 2005 10:45:25 +0100 (MET)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
 by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
 id 12752-15; Sun, 13 Feb 2005 10:45:24 +0100 (MET)
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP;
Sun, 13 Feb 2005 10:45:24 +0100 (MET)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id j1D9jND5007014;
Sun, 13 Feb 2005 10:45:23 +0100 (MET)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 13 Feb 2005 10:45:23 +0100
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: fixed in gcc-snapshot_20050212-1
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 
X-CrossAssassin-Score: 2

fixed in gcc-snapshot_20050212-1


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

Bug#284667: marked as done (gfortran not in gcc-snapshot)

2005-02-13 Thread Debian Bug Tracking System 
Your message dated Sun, 13 Feb 2005 10:45:23 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-snapshot_20050212-1
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)

--
Received: (at submit) by bugs.debian.org; 7 Dec 2004 21:08:50 +
>From [EMAIL PROTECTED] Tue Dec 07 13:08:49 2004
Return-path: <[EMAIL PROTECTED]>
Received: from rock.esc.cam.ac.uk [131.111.41.250] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CbmZl-00072I-00; Tue, 07 Dec 2004 13:08:49 -0800
Received: from parabrisas.esc.cam.ac.uk ([131.111.44.165] ident=Debian-exim)
by rock.esc.cam.ac.uk with esmtp (Exim 4.34)
id 1CbmZi-0006GS-Ty; Tue, 07 Dec 2004 21:08:48 +
Received: from tow by parabrisas.esc.cam.ac.uk with local (Exim 4.34)
id 1CbmZi-0007lH-RC; Tue, 07 Dec 2004 21:08:46 +
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: [EMAIL PROTECTED]
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gfortran not in gcc-snapshot
X-Mailer: reportbug 3.2
Date: Tue, 07 Dec 2004 21:08:46 +
Message-Id: <[EMAIL PROTECTED]>
Sender: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.2 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS,
HAS_PACKAGE,NO_REAL_NAME autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: gcc-snapshot
Version: 20041030-1
Severity: normal


gcc-snapshot of 20040704 included gfortran; I've just upgraded to 
20041030, and gfortran is no longer there. Given that gfortran is 
one of the more high-profile developments in gcc-4.0.0, it would seem
important to include it.

Toby


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (101, 'testing'), (99, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to 
en_GB)

Versions of packages gcc-snapshot depends on:
ii  binutils2.15-5   The GNU assembler, linker and bina
ii  libart-2.0-22.3.16-6 Library of functions for 2D graphi
ii  libatk1.0-0 1.8.0-3  The ATK accessibility toolkit
ii  libc6   2.3.2.ds1-18 GNU C Library: Shared libraries an
ii  libglib2.0-02.4.7-1  The GLib library of C routines
ii  libgtk2.0-0 2.4.13-1 The GTK+ graphical user interface 
ii  libpango1.0-0   1.6.0-3  Layout and rendering of internatio
ii  zlib1g  1:1.2.2-3compression library - runtime

-- no debconf information

---
Received: (at 284667-done) by bugs.debian.org; 13 Feb 2005 09:45:28 +
>From [EMAIL PROTECTED] Sun Feb 13 01:45:28 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D0GJk-0007vI-00; Sun, 13 Feb 2005 01:45:28 -0800
Received: from mailhost.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.17.13])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id KAA17815;
Sun, 13 Feb 2005 10:45:26 +0100 (MET)
Received: from localhost (localhost [127.0.0.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 7E4C3F215;
Sun, 13 Feb 2005 10:45:25 +0100 (MET)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
 by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
 id 12752-15; Sun, 13 Feb 2005 10:45:24 +0100 (MET)
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP;
Sun, 13 Feb 2005 10:45:24 +0100 (MET)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id j1D9jND5007014;
Sun, 13 Feb 2005 10:45:23 +0100 (MET)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 13 Feb 2005 10:45:23 +0100
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: fixed in gcc-snapshot_20050212-1
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.de

unsubscribe

2005-02-13 Thread Bernhard Busch 
unsubscribe
--
Dr. Bernhard Busch
Max-Planck-Institut für Biochemie
Rechenzentrum
Am Klopferspitz 18a
D-82152 Martinsried
Tel: +49(89)8578-2582
Fax: +49(89)8578-2479
Email [EMAIL PROTECTED]

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

Bug#295073: g++-3.3: operator new doesn't initialize memory anymore after thrown exception

2005-02-13 Thread Frank B. Brokken 
Package: g++-3.3
Version: 1:3.3.5-5
Severity: normal


Dear g++ maintainer,

When running the following little program it appears that operator new fails
to initialize the memory it allocates. For example, when I run the program I
get the following output:

134517800 0 1074470752 1074986304 0 1 1 134517181 134517168 134515206 

The program was compiled using both a plain `g++' command and `g++ -Wall
-fexceptions'. No warnings are reported and compilation proceeds flawlessly. 

Here is the program;


#include 
#include 
#include 

using namespace std;

void showalloc()
{
int *ip = new int [10];

copy(ip, ip + 10, ostream_iterator(cerr, " "));

cout << endl;

delete [] ip;
}

void thrower()
{
try
{
throw 0;// remove this to obtain memory initialized to 0
}
catch(...)
{}
}

int main()
{
thrower();
showalloc();
return 0;
}


When the `throw 0;' statement is removed the memory comes out neatly
initialized. The program's output in that case is:

0 0 0 0 0 0 0 0 0 0 

Kind regards,

Frank B. Brokken

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages g++-3.3 depends on:
ii  gcc-3.3 1:3.3.5-5The GNU C compiler
ii  gcc-3.3-base1:3.3.5-5The GNU Compiler Collection (base 
ii  libc6   2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libstdc++5-3.3-dev  1:3.3.5-5The GNU Standard C++ Library v3 (d

-- no debconf information


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

[Bug libgcj/19934] [4.0 regression] [alpha-linux] bootstrap error linking libgcj

2005-02-13 Thread pinskia at gcc dot gnu dot org 

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-02-13 
13:55 ---
Confirmed.
See  for a possible 
patch and 
discussion.

-- 
   What|Removed |Added

 Status|UNCONFIRMED |NEW
  Component|target  |libgcj
 Ever Confirmed||1
   Keywords||build
   Last reconfirmed|-00-00 00:00:00 |2005-02-13 13:55:12
   date||


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

--- 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#295073: marked as done (g++-3.3: operator new doesn't initialize memory anymore after thrown exception)

2005-02-13 Thread Debian Bug Tracking System 
Your message dated Sun, 13 Feb 2005 14:55:24 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#295073: g++-3.3: operator new doesn't initialize memory 
anymore after thrown exception
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)

--
Received: (at submit) by bugs.debian.org; 13 Feb 2005 13:25:43 +
>From [EMAIL PROTECTED] Sun Feb 13 05:25:43 2005
Return-path: <[EMAIL PROTECTED]>
Received: from oosix.icce.rug.nl [129.125.14.80] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D0Jkt-0006C6-00; Sun, 13 Feb 2005 05:25:43 -0800
Received: from knarfix.oostum.north (knarfix.oostum.north [129.125.100.246])
by oosix.icce.rug.nl (8.13.2/8.13.2/Debian-1) with ESMTP id 
j1DDPCvq031960
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Sun, 13 Feb 2005 14:25:12 +0100
Received: from knarfix.oostum.north (localhost [127.0.0.1])
by knarfix.oostum.north (8.13.2/8.13.2/Debian-1) with ESMTP id 
j1DDP6br001529
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Sun, 13 Feb 2005 14:25:06 +0100
Received: (from [EMAIL PROTECTED])
by knarfix.oostum.north (8.13.2/8.13.2/Submit) id j1DDP6A4001528;
Sun, 13 Feb 2005 14:25:06 +0100
Message-Id: <[EMAIL PROTECTED]>
X-Authentication-Warning: knarfix.oostum.north: frank set sender to [EMAIL 
PROTECTED] using -f
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Frank B. Brokken" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: g++-3.3: operator new doesn't initialize memory anymore after thrown
 exception
X-Mailer: reportbug 3.2
Date: Sun, 13 Feb 2005 14:25:05 +0100
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: g++-3.3
Version: 1:3.3.5-5
Severity: normal


Dear g++ maintainer,

When running the following little program it appears that operator new fails
to initialize the memory it allocates. For example, when I run the program I
get the following output:

134517800 0 1074470752 1074986304 0 1 1 134517181 134517168 134515206 

The program was compiled using both a plain `g++' command and `g++ -Wall
-fexceptions'. No warnings are reported and compilation proceeds flawlessly. 

Here is the program;


#include 
#include 
#include 

using namespace std;

void showalloc()
{
int *ip = new int [10];

copy(ip, ip + 10, ostream_iterator(cerr, " "));

cout << endl;

delete [] ip;
}

void thrower()
{
try
{
throw 0;// remove this to obtain memory initialized to 0
}
catch(...)
{}
}

int main()
{
thrower();
showalloc();
return 0;
}


When the `throw 0;' statement is removed the memory comes out neatly
initialized. The program's output in that case is:

0 0 0 0 0 0 0 0 0 0 

Kind regards,

Frank B. Brokken

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages g++-3.3 depends on:
ii  gcc-3.3 1:3.3.5-5The GNU C compiler
ii  gcc-3.3-base1:3.3.5-5The GNU Compiler Collection (base 
ii  libc6   2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libstdc++5-3.3-dev  1:3.3.5-5The GNU Standard C++ Library v3 (d

-- no debconf information

---
Received: (at 295073-done) by bugs.debian.org; 13 Feb 2005 13:55:57 +
>From [EMAIL PROTECTED] Sun Feb 13 05:55:56 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp07.web.de [217.72.192.225] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D0KE8-0001ml-00; Sun, 13 Feb 2005 05:55:56 -0800
Received: from [80.144.178.220] (helo=juist)
by smtp07.web.de with asmtp (TLSv1:DES-CBC3-SHA:168)
(WEB.DE 4.103 #192)
id 1D0KDd-00045r-00
for [EMAIL PROTECTED]; Sun, 13 Feb 2005 14:55:26 +0100
Received: from falk by juist with local (Exim 4.44)
id 1D0KDc-la-43
for [EMAIL PROTECTED]; Sun, 13 Feb 2005 14:55:24 +0100
T

Results for 4.0.0 20050212 (experimental) testsuite on i486-pc-linux-gnu

2005-02-13 Thread Matthias Klose 
LAST_UPDATED: Sat Feb 12 20:53:45 UTC 2005

=== acats tests ===
FAIL:   a26007a
FAIL:   ad8011a
FAIL:   c23003a
FAIL:   c23003b
FAIL:   c23003g
FAIL:   c23003i
FAIL:   c32001e
FAIL:   c34002a
FAIL:   c35502d
FAIL:   c35502f
FAIL:   c35503d
FAIL:   c35503f
FAIL:   c391002
FAIL:   c432002
FAIL:   c43214c
FAIL:   c45231d
FAIL:   c460007
FAIL:   c4a007a
FAIL:   c52011a
FAIL:   c64105b
FAIL:   c85006e
FAIL:   c87b62d
FAIL:   c95086b
FAIL:   c96005b
FAIL:   cc1221d
FAIL:   cc1225a
FAIL:   cd10001
FAIL:   cd1009k
FAIL:   cd1009t
FAIL:   cd1009u
FAIL:   cd1c03e
FAIL:   cd1c06a
FAIL:   cd2a83c
FAIL:   cd2a91c
FAIL:   cd2b11a
FAIL:   cd2b11b
FAIL:   cd2c11a
FAIL:   cd2c11d
FAIL:   cd30001
FAIL:   cd4041a
FAIL:   cd5003a
FAIL:   cd5003b
FAIL:   cd5003c
FAIL:   cd5003d
FAIL:   cd5003e
FAIL:   cd5003f
FAIL:   cd5003g
FAIL:   cd5003h
FAIL:   cd5003i
FAIL:   cd5011a
FAIL:   cd5011c
FAIL:   cd5011e
FAIL:   cd5011g
FAIL:   cd5011i
FAIL:   cd5011k
FAIL:   cd5011m
FAIL:   cd5011q
FAIL:   cd5011s
FAIL:   cd5012a
FAIL:   cd5012b
FAIL:   cd5012e
FAIL:   cd5012f
FAIL:   cd5012i
FAIL:   cd5012m
FAIL:   cd5013a
FAIL:   cd5013c
FAIL:   cd5013e
FAIL:   cd5013g
FAIL:   cd5013i
FAIL:   cd5013k
FAIL:   cd5013m
FAIL:   cd5013o
FAIL:   cd5014a
FAIL:   cd5014c
FAIL:   cd5014e
FAIL:   cd5014g
FAIL:   cd5014i
FAIL:   cd5014k
FAIL:   cd5014m
FAIL:   cd5014o
FAIL:   cd5014t
FAIL:   cd5014v
FAIL:   cd5014x
FAIL:   cd5014y
FAIL:   cd5014z
FAIL:   cd7101g
FAIL:   cdd2a02
FAIL:   ce2102c
FAIL:   ce2102h
FAIL:   ce2103a
FAIL:   ce2103b
FAIL:   ce2203a
FAIL:   ce2403a
FAIL:   ce3002b
FAIL:   ce3002c
FAIL:   ce3102b
FAIL:   ce3107a
FAIL:   ce3304a
FAIL:   cxa3004
FAIL:   cxa4006
FAIL:   cxa4017
FAIL:   cxb3006

=== acats Summary ===
# of expected passes2220
# of unexpected failures102
Native configuration is i486-pc-linux-gnu

=== g++ tests ===


Running target unix
XPASS: g++.old-deja/g++.other/init5.C execution test

=== g++ Summary ===

# of expected passes10699
# of unexpected successes   1
# of expected failures  69
# of unsupported tests  56
/home/packages/gcc/snap/gcc-snapshot-20050212/build/gcc/testsuite/../g++  
version 4.0.0 20050212 (experimental)

=== gcc tests ===


Running target unix
XPASS: gcc.dg/tree-ssa/20040204-1.c scan-tree-dump-times link_error 0
XPASS: gcc.dg/vect/vect-22.c scan-tree-dump-times vectorized 3 loops 1

=== gcc Summary ===

# of expected passes33021
# of unexpected successes   2
# of expected failures  88
# of untested testcases 28
# of unsupported tests  307
/home/packages/gcc/snap/gcc-snapshot-20050212/build/gcc/xgcc  version 4.0.0 
20050212 (experimental)

=== gfortran tests ===


Running target unix
XPASS: gfortran.dg/ret_pointer_1.f90  -O0  execution test
XPASS: gfortran.dg/ret_pointer_1.f90  -O1  execution test
XPASS: gfortran.dg/ret_pointer_1.f90  -O2  execution test
XPASS: gfortran.dg/ret_pointer_1.f90  -O3 -fomit-frame-pointer  execution test
XPASS: gfortran.dg/ret_pointer_1.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
XPASS: gfortran.dg/ret_pointer_1.f90  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions  execution test
XPASS: gfortran.dg/ret_pointer_1.f90  -O3 -g  execution test
XPASS: gfortran.dg/ret_pointer_1.f90  -Os  execution test
FAIL: gfortran.fortran-torture/execute/forall_3.f90 execution,  -O1 

=== gfortran Summary ===

# of expected passes5220
# of unexpected failures1
# of unexpected successes   8
# of expected failures  18
# of unsupported tests  8
/home/packages/gcc/snap/gcc-snapshot-20050212/build/gcc/testsuite/../gfortran  
version 4.0.0 20050212 (experimental)

=== objc tests ===


Running target unix

=== objc Summary ===

# of expected passes1534
# of unsupported tests  10
/home/packages/gcc/snap/gcc-snapshot-20050212/build/gcc/xgcc  version 4.0.0 
20050212 (experimental)

=== libffi tests ===


Running target unix

=== libffi Summary ===

# of expected passes216
# of unsupported tests  2
=== libjava tests ===


Running target unix

=== libjava Summary ===

# of expected passes3726
# of expected failures  14
# of untested testcases 16
=== libmudflap tests ===


Running target unix

=== libmudflap Summary ===

# of expected passes1280

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

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

using: 
/home/packages/gcc/snap/gcc-snapshot-20050212/src/libstdc++-v3/config/abi/i486-linux-gnu/baseline_symbols.txt

=== libstdc++ tests ===


Running target unix
XPASS: 22_locale/locale/

Results for 3.4.4 20050203 (prerelease) (Debian 3.4.3-9) testsuite on m68k-linux

2005-02-13 Thread Matthias Klose 
LAST_UPDATED: Mon Feb  7 22:07:14 UTC 2005

Native configuration is m68k-linux (a4000t)

=== gpc tests ===


Running target any
FAIL: emil24.pas
FAIL: fjf328.pas
FAIL: fjf347.pas
FAIL: kurzw2.pas

=== gpc Summary ===

# of tests3953
# of expected passes  3946
# of unexpected failures  4
# of unsupported tests3
/build/buildd/gcc-3.4-3.4.3/build/gcc/xgpc version 20040516, based on gcc-3.4.4 
20050203 (prerelease) (Debian 3.4.3-9)

=== g++ tests ===


Running target unix
FAIL: g++.dg/abi/bitfield4.C execution test
FAIL: g++.dg/eh/omit-frame-pointer.C execution test
FAIL: g++.dg/eh/registers1.C execution test
XPASS: g++.dg/rtti/tinfo1.C scan-assembler _ZTIP9CTemplateIhE:
XPASS: g++.dg/rtti/tinfo1.C scan-assembler-not .globl[ \\t]+_ZTIP9CTemplateIhE
FAIL: g++.old-deja/g++.eh/ia64-1.C execution test
WARNING: g++.old-deja/g++.mike/p10769a.C compilation failed to produce 
executable
WARNING: g++.old-deja/g++.other/enum5.C compilation failed to produce executable
XPASS: g++.old-deja/g++.other/init5.C execution test
WARNING: g++.old-deja/g++.pt/friend44.C compilation failed to produce executable

=== g++ Summary ===

# of expected passes9705
# of unexpected failures4
# of unexpected successes   3
# of expected failures  71
# of unsupported tests  83
/build/buildd/gcc-3.4-3.4.3/build/gcc/testsuite/../g++  version 3.4.4 20050203 
(prerelease) (Debian 3.4.3-9)

=== g77 tests ===


Running target unix

=== g77 Summary ===

# of expected passes1812
# of unsupported tests  6
/build/buildd/gcc-3.4-3.4.3/build/gcc/testsuite/../g77  version 3.4.4 20050203 
(prerelease) (Debian 3.4.3-9)

=== gcc tests ===


Running target unix
FAIL: gcc.c-torture/compile/921118-1.c  -O3 -fomit-frame-pointer  (test for 
excess errors)
FAIL: gcc.c-torture/compile/921118-1.c  -O3 -g  (test for excess errors)
FAIL: gcc.c-torture/execute/builtins/string-3.c execution,  -O1 
FAIL: gcc.c-torture/execute/builtins/string-3.c execution,  -O2 
FAIL: gcc.c-torture/execute/builtins/string-3.c execution,  -O3 
-fomit-frame-pointer 
FAIL: gcc.c-torture/execute/builtins/string-3.c execution,  -O3 -g 
FAIL: gcc.c-torture/execute/builtins/string-3.c execution,  -Os 
FAIL: gcc.c-torture/execute/20001108-1.c execution,  -O3 -fomit-frame-pointer 
FAIL: gcc.c-torture/execute/20001108-1.c execution,  -O3 -g 
FAIL: gcc.c-torture/execute/20001203-2.c execution,  -O3 -fomit-frame-pointer 
FAIL: gcc.c-torture/execute/20001203-2.c execution,  -O3 -g 
FAIL: gcc.c-torture/execute/20020418-1.c execution,  -O1 
FAIL: gcc.c-torture/execute/20020418-1.c execution,  -O2 
FAIL: gcc.c-torture/execute/20020418-1.c execution,  -Os 
FAIL: gcc.c-torture/execute/20020720-1.c compilation,  -O1 
UNRESOLVED: gcc.c-torture/execute/20020720-1.c execution,  -O1 
FAIL: gcc.c-torture/execute/930921-1.c execution,  -O3 -fomit-frame-pointer 
-funroll-loops 
FAIL: gcc.c-torture/execute/930921-1.c execution,  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions 
FAIL: gcc.c-torture/execute/950511-1.c compilation,  -O3 -fomit-frame-pointer 
UNRESOLVED: gcc.c-torture/execute/950511-1.c execution,  -O3 
-fomit-frame-pointer 
FAIL: gcc.c-torture/execute/950511-1.c compilation,  -O3 -g 
UNRESOLVED: gcc.c-torture/execute/950511-1.c execution,  -O3 -g 
FAIL: gcc.c-torture/execute/961213-1.c execution,  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O0 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O1 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O2 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O3 -fomit-frame-pointer 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O3 -fomit-frame-pointer 
-funroll-loops 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -O3 -g 
FAIL: gcc.c-torture/execute/loop-2f.c execution,  -Os 
FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O0 
FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O1 
FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O2 
FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O3 -fomit-frame-pointer 
FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O3 -fomit-frame-pointer 
-funroll-loops 
FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions 
FAIL: gcc.c-torture/execute/loop-2g.c execution,  -O3 -g 
FAIL: gcc.c-torture/execute/loop-2g.c execution,  -Os 
FAIL: gcc.dg/bitfld-3.c execution test
FAIL: gcc.dg/bitfld-4.c execution test
XPASS: gcc.dg/c99-flex-array-4.c sizeof != offsetof (test for bogus messages, 
line 24)
FAIL: gcc.dg/pack-test-1.c (test for excess errors)
XPASS: gcc.dg/sibcall-3.c execution test
XPASS: gcc.dg/sibcall-4.c execution test
FAIL: gcc.dg/weak/typeof-2.c scan-assem