public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Randolph Chung <tausq@debian.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: [parisc-linux] Re: c++/10235: [3.3 regression] [HPPA] internal compiler error: in final_scan_insn, at final.c:2099
Date: Thu, 17 Apr 2003 06:26:00 -0000	[thread overview]
Message-ID: <20030417062601.29094.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/10235; it has been noted by GNATS.

From: Randolph Chung <tausq@debian.org>
To: doko@gcc.gnu.org, debian-gcc@lists.debian.org,
	gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	parisc-linux@lists.parisc-linux.org, gcc-gnats@gcc.gnu.org,
	danglin@gcc.gnu.org
Cc:  
Subject: Re: [parisc-linux] Re: c++/10235: [3.3 regression] [HPPA] internal compiler error: in final_scan_insn, at final.c:2099
Date: Wed, 16 Apr 2003 23:19:58 -0700

 In reference to a message from doko@gcc.gnu.org, dated Apr 17:
 > Synopsis: [3.3 regression] [HPPA] internal compiler error: in final_scan_insn, at final.c:2099
 > 
 > State-Changed-From-To: feedback->closed
 > State-Changed-By: doko
 > State-Changed-When: Thu Apr 17 05:57:39 2003
 > State-Changed-Why:
 >     sucessfully built as well with 3.3 20030412 (current Debian package)
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10235
 
 really? it still ICEs for me with that version. The test case was from
 the nurbs++ package.
 
 tausq@ios:~/debian/nurbs++-3.0.11$ g++ -v
 Reading specs from /usr/lib/gcc-lib/hppa-linux/3.3/specs
 Configured with: ../src/configure -v --enable-languages=c,c++,f77,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-sjlj-exceptions --enable-clocale=gnu --enable-debug --enable-objc-gc hppa-linux
 Thread model: posix
 gcc version 3.3 20030412 (Debian prerelease)
 
 tausq@ios:~/debian/nurbs++-3.0.11$ g++ -DHAVE_CONFIG_H -I. -I. -I../include -I/usr/X11R6/include -I../include -I../matrix -I../image -I../numerical -g -O2 -fno-implicit-templates -c f_nurbs.cpp -MT f_nurbs.lo -MD -MP -MF .deps/f_nurbs.TPlo  -fPIC -DPIC -o .libs/f_nurbs.lo
 nurbs.cpp: In member function `void PLib::NurbsCurve<T, N>::globalInterpD(const
    PLib::Vector<PLib::Point_nD<T, D> >&, const PLib::Vector<PLib::Point_nD<T,
    D> >&, int, int, T) [with T = float, int N = 2]':
 f_nurbs.cpp:85:   instantiated from here
 nurbs.cpp:3060: internal compiler error: in final_scan_insn, at final.c:2099
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://gcc.gnu.org/bugs.html> for instructions.
 
 Maybe the test case needs fixing :) Dave, I'll put a preprocessed file
 in gsyprf11:~tausq/f_nurbs.ii.gz. It's >100k so i won't post it here 
 for now.  :)
 
 i'm in the process of building a new cvs snapshot to retry.
 
 thanks,
 randolph
 -- 
 Randolph Chung
 Debian GNU/Linux Developer, hppa/ia64 ports
 http://www.tausq.org/


             reply	other threads:[~2003-04-17  6:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17  6:26 Randolph Chung [this message]
2003-04-17 13:26 John David Anglin

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=20030417062601.29094.qmail@sources.redhat.com \
    --to=tausq@debian.org \
    --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).