public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dLux <dlux@dlux.hu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/4712: Internal compiler error with -O2 in except.c:2723
Date: Thu, 01 Nov 2001 07:54:00 -0000	[thread overview]
Message-ID: <20011112000600.15101.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR optimization/4712; it has been noted by GNATS.

From: dLux <dlux@dlux.hu>
To: rodrigc@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: optimization/4712: Internal compiler error with -O2 in except.c:2723
Date: Mon, 12 Nov 2001 00:32:39 +0100

 --opJtzjQTFsWo+cga
 Content-Type: text/plain; charset=iso-8859-1
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 /--- On Sat, Nov 10, 2001 at 04:12:56AM -0000, rodrigc@gcc.gnu.org wrote:
 | State-Changed-From-To: open->feedback
 | State-Changed-By: rodrigc
 | State-Changed-When: Fri Nov  9 20:12:56 2001
 | State-Changed-Why:
 |     I could not reproduce your ICE.  I could successfully compile
 |     your code example.  Here is my configuration:
 |    =20
 |     Reading specs from /u0/test/gcc/lib/gcc-lib/i686-pc-linux-gnu/3.0.2/s=
 pecs
 |     Configured with: ./configure --prefix=3D/u0/test/gcc --enable-checkin=
 g --enable-languages=3Dc,c++ : (reconfigured) ./configure --prefix=3D/u0/te=
 st/gcc --enable-checking --enable-languages=3Dc,c++ --enable-shared --enabl=
 e-threads
 |     Thread model: posix
 |     gcc version 3.0.2
 |    =20
 |     Is your installation misconfigured somehow?
 |=20
 | http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&pr=3D4712=
 &database=3Dgcc
 \---
 
 Strange. I have tried again, and I have found the same problem.
 As I see the difference from the configuration it can be the problem of:
 - i386 optimizer
 - debian packaging
 - --long-long support
 - --nls support
 - faulty hardware (processor?)
 
 This macihne is a mobile PIII/650 with the following CPUinfo.=20
 
 This is my cpuinfo:
 
 processor       : 0
 vendor_id       : GenuineIntel
 cpu family      : 6
 model           : 8
 model name      : Pentium III (Coppermine)
 stepping        : 6
 cpu MHz         : 648.285
 cache size      : 256 KB
 fdiv_bug        : no
 hlt_bug         : no
 f00f_bug        : no
 coma_bug        : no
 fpu             : yes
 fpu_exception   : yes
 cpuid level     : 2
 wp              : yes
 flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca
 cmov pat pse36 mmx fxsr sse
 bogomips        : 1294.33
 
 The system is a stock debian with glibc 2.2.4
 
 What can I do to help you discovering this bug?
 
 Other info (these were in the bug report also):
 
 dlux@dl:~$ gcc-3.0 -v
 Reading specs from /usr/lib/gcc-lib/i386-linux/3.0.2/specs
 Configured with: ../src/configure -v --enable-languages=3Dc,c++,java,f77,pr=
 oto,objc --prefix=3D/usr --infodir=3D/share/info --mandir=3D/share/man --en=
 able-shared --with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-lo=
 ng --enable-nls --without-included-gettext --disable-checking --enable-thre=
 ads=3Dposix --enable-java-gc=3Dboehm --with-cpp-install-dir=3Dbin --enable-=
 objc-gc i386-linux
 Thread model: posix
 gcc version 3.0.2 (Debian)
 
 dLux
 --
 	       ... V=E9gy egy Magnumot =E9s fogd r=E1 a Nyuszira!
 
 --opJtzjQTFsWo+cga
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.0.6 (GNU/Linux)
 Comment: For info see http://www.gnupg.org
 
 iD8DBQE77wqWP2lOlowILeYRAsjkAJ4hR5tycXkIXLJbhZ7Dt8OCZ7O7OgCcDbur
 cxQ9ZFnXsXPa97488ND52q4=
 =lcaI
 -----END PGP SIGNATURE-----
 
 --opJtzjQTFsWo+cga--


                 reply	other threads:[~2001-11-12  0:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011112000600.15101.qmail@sourceware.cygnus.com \
    --to=dlux@dlux.hu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).