public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jocelyn.etienne@imag.fr
To: gcc-gnats@gcc.gnu.org
Subject: c++/6034: Internal compiler error in `output_fix_trunc'
Date: Fri, 22 Mar 2002 00:16:00 -0000 [thread overview]
Message-ID: <20020322081217.15032.qmail@sources.redhat.com> (raw)
>Number: 6034
>Category: c++
>Synopsis: Internal compiler error in `output_fix_trunc'
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Mar 22 00:16:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: jocelyn.etienne@imag.fr
>Release: gcc version 2.95.4 (Debian prerelease)
>Organization:
>Environment:
Linux machine 2.4.17 #3 SMP Wed Jan 23 10:27:24 GMT 2002 i686 unknown
>Description:
c++ -O2 -fno-inline-functions -I/home/jocelyn/Sys/include -I/home/jocelyn/Sys/lib -L/home/jocelyn/Sys/lib -lfem -lskit -lutil test.cc hazel.o -o test
test.cc: In method `Float hazel::evaluate(const meshpoint &, const geo_element &, const field &)':
test.cc:41: warning: assignment to `unsigned int' from `Float'
test.cc:43: no matching function for call to `base::reference_eval (const geo_element &, tiny_vector<unsigned int> &, point) const'
/home/jocelyn/Sys/include/rheolef/base_declare.h:136: candidates are: Float base::reference_eval(reference_element, const tiny_vector<double> &, const point &) const
test.cc:44: Internal compiler error:
test.cc:44: Internal compiler error in `output_fix_trunc', at config/i386/i386.c:4012
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make: *** [test] Error 1
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-03-22 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-22 0:16 jocelyn.etienne [this message]
2002-03-22 19:35 rodrigc
2002-04-20 13:31 rodrigc
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=20020322081217.15032.qmail@sources.redhat.com \
--to=jocelyn.etienne@imag.fr \
--cc=gcc-gnats@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).