Your message dated Sat, 22 Jan 2005 14:20:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#291605: gcc-4.0: GCC4 internal compiler error:
Segmentation fault
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; 21 Jan 2005 19:25:39 +0000
>From [EMAIL PROTECTED] Fri Jan 21 11:25:39 2005
Return-path: <[EMAIL PROTECTED]>
Received: from amber.ccs.neu.edu [129.10.116.51]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Cs4Pb-0006uZ-00; Fri, 21 Jan 2005 11:25:39 -0800
Received: from portuguese.ccs.neu.edu ([129.10.116.249]
helo=localhost.localdomain)
by amber.ccs.neu.edu with esmtp (Exim 4.34)
id 1Cs4PS-0004oG-Kf; Fri, 21 Jan 2005 14:25:30 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Daniel Silva <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gcc-4.0: GCC4 internal compiler error: Segmentation fault
Bcc: Daniel Silva <[EMAIL PROTECTED]>
X-Mailer: reportbug 3.5
Date: Fri, 21 Jan 2005 14:25:26 -0500
Message-Id: <[EMAIL PROTECTED]>
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: gcc-4.0
Version: 4.0-0pre2
Severity: grave
Tags: experimental
Justification: renders package unusable
While running configure for the Mono runtime:
configure:3030: checking for gcc option to accept ANSI C
configure:3100: gcc -c -march=pentium3 -O2 -foptimize-sibling-calls
-finline-functions -fmerge-constants -fmerge-all-constants
-funroll-loops -fnew-ra -fprefetch-loop-arrays -ffast-math
-fno-math-errno -funsafe-math-optimizations -ffinite-math-only
-fno-trapping-math -fsignaling-nans -fsingle-precision-constant
-ftree-loop-linear -funswitch-loops -fivopts -ftree-sra -ftree-vectorize
-fweb -fvariable-expansion-in-unroller -freorder-blocks-and-partition
-funit-at-a-time -fbranch-target-load-optimize -DGC_LINUX_THREADS
-D_GNU_SOURCE -D_REENTRANT conftest.c >&5
conftest.c: In function 'main':
conftest.c:55: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see <URL:file:///usr/share/doc/gcc-4.0/README.Bugs>.
configure:3106: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "mono"
| #define VERSION "1.1.3"
| /* end confdefs.h. */
| #include <stdarg.h>
| #include <stdio.h>
| #include <sys/types.h>
| #include <sys/stat.h>
| /* Most of the following tests are stolen from RCS 5.7's src/conf.sh.
*/
| struct buf { int x; };
| FILE * (*rcsopen) (struct buf *, struct stat *, int);
| static char *e (p, i)
| char **p;
| int i;
| {
| return p[i];
| }
| static char *f (char * (*g) (char **, int), char **p, ...)
| {
| char *s;
| va_list v;
| va_start (v,p);
| s = g (p, va_arg (v,int));
| va_end (v);
| return s;
| }
|
| /* OSF 4.0 Compaq cc is some sort of almost-ANSI by default. It has
| function prototypes and stuff, but not '\xHH' hex character
constants.
| These don't provoke an error unfortunately, instead are silently
treated
| as 'x'. The following induces an error, until -std1 is added to
get
| proper ANSI mode. Curiously '\x00'!='x' always comes out true, for
an
| array size at least. It's necessary to write '\x00'==0 to get
something
| that's true only with -std1. */
| int osf4_cc_array ['\x00' == 0 ? 1 : -1];
|
| int test (int i, double x);
| struct s1 {int (*f) (int a);};
| struct s2 {int (*f) (double a);};
| int pairnames (int, char **, FILE *(*)(struct buf *, struct stat *,
int), int, int);
| int argc;
| char **argv;
| int
| main ()
| {
| return f (e, argv, 0) != argv[0] || f (e, argv, 1) != argv[1];
| ;
| return 0;
| }
$ env | grep DEB
DEBIAN_BUILDGCCVER=4.0
DEBIAN_BUILDARCH=pentium3
$ gcc --version
gcc-4.0 (GCC) 4.0.0 20041205 (experimental) (Debian 4.0-0pre2)
$ echo $CFLAGS
-march=pentium3 -O2 -foptimize-sibling-calls -finline-functions
-fmerge-constants -fmerge-all-constants -funroll-loops -fnew-ra
-fprefetch-loop-arrays -ffast-math -fno-math-errno
-funsafe-math-optimizations -ffinite-math-only -fno-trapping-math
-fsignaling-nans -fsingle-precision-constant -ftree-loop-linear
-funswitch-loops -fivopts -ftree-sra -ftree-vectorize -fweb
-fvariable-expansion-in-unroller -freorder-blocks-and-partition
-funit-at-a-time -fbranch-target-load-optimize
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages gcc-4.0 depends on:
ii binutils 2.15-5 The GNU assembler, linker and bina
ii cpp-4.0 4.0-0pre2 The GNU C preprocessor
ii gcc-4.0-base 4.0-0pre2 The GNU Compiler Collection (base
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libgcc1 1:4.0-0pre2 GCC support library
-- no debconf information
---------------------------------------
Received: (at 291605-done) by bugs.debian.org; 22 Jan 2005 13:19:52 +0000
>From [EMAIL PROTECTED] Sat Jan 22 05:19:51 2005
Return-path: <[EMAIL PROTECTED]>
Received: from lc08.rz.uni-jena.de [141.35.1.23]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CsLB9-0004Fn-00; Sat, 22 Jan 2005 05:19:51 -0800
Received: from binwachsam.rz.uni-jena.de (binwachsam.rz.uni-jena.de
[141.35.1.24])
by lc08.rz.uni-jena.de (8.12.8/8.12.8) with ESMTP id j0MDJnUo014157;
Sat, 22 Jan 2005 14:19:49 +0100
Received: from localhost (localhost.localdomain [127.0.0.1])
by binwachsam.rz.uni-jena.de (8.11.6/8.11.6) with ESMTP id j0MDJnA07613;
Sat, 22 Jan 2005 14:19:49 +0100
Received: from binwachsam.rz.uni-jena.de ([127.0.0.1])
by localhost (binwachsam.rz.uni-jena.de [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 07528-03; Sat, 22 Jan 2005 14:19:49 +0100 (CET)
Received: from lc08.rz.uni-jena.de (lc08.rz.uni-jena.de [141.35.1.23])
by binwachsam.rz.uni-jena.de (8.11.6/8.11.6) with ESMTP id j0MDJn607607;
Sat, 22 Jan 2005 14:19:49 +0100
Received: from pax08e3.mipool.uni-jena.de (pax08e1.mipool.uni-jena.de
[141.35.13.44])
by lc08.rz.uni-jena.de (8.12.8/8.12.8) with ESMTP id j0MDJn2S014154;
Sat, 22 Jan 2005 14:19:49 +0100
Received: from ipc705.mipool.uni-jena.de ([EMAIL PROTECTED] [141.35.12.61])
by pax08e3.mipool.uni-jena.de (8.12.10/8.12.10) with SMTP id
j0MDJmZS313929;
Sat, 22 Jan 2005 14:19:48 +0100 (CET)
Received: by ipc705.mipool.uni-jena.de (sSMTP sendmail emulation); Sat, 22 Jan
2005 14:20:59 +0100
Date: Sat, 22 Jan 2005 14:20:59 +0100
From: [EMAIL PROTECTED]
To: Daniel Pinto de Mello e Silva <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#291605: gcc-4.0: GCC4 internal compiler error: Segmentation
fault
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new at uni-jena.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=-4.4 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
NO_REAL_NAME autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
On Fri, Jan 21, 2005 at 03:12:52PM -0500, Daniel Pinto de Mello e Silva wrote:
> The compiler error goes away without -fnew-ra. Should I send you
> any other errors that come up with -fnew-ra in the future to help
> with testing/debugging?
No, the new-ra project has been abandoned upstream. So closing.
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
