From: Joe Buck <jbuck@synopsys.com>
To: egcs@cygnus.com (egcs team)
Subject: internal compiler error in C++ front end
Date: Sun, 28 Sep 1997 15:49:00 -0000 [thread overview]
Message-ID: <199709282248.PAA07344@atrus.synopsys.com> (raw)
The following program blows up egcs (every version since at least 970910
through the present version):
#include <vector>
vector<int> v(3,5);
I've verified that the crash occurs on both Linux and Solaris/sparc.
The message is
/usr/local/egcs/include/g++/vector.h:103: Internal compiler error 97.
/usr/local/egcs/include/g++/vector.h:103: Please submit a full bug report
to `egcs-bugs@cygnus.com'.
vector<double> v(5, 3.0);
works fine.
vector<double> v(3.0, 5);
is quietly accepted, but seems bogus. I suppose the compiler can
assume InputIterator == double, but this seems strange.
does not crash, but
vector<double> v(3, 5);
does: so does the illegal
vector<double> v(3.0, 3.0);
It seems that there is some confusion between vector<T>(size_type,const T&)
and the template member vector<T>(Iterator,Iterator). The odd thing
is that for vector<int>(32,3) the second seems in some ways a better match,
but STL is banking on the first one being chosen! (to get a vector of
32 elements with value 3).
While it's likely that this particular case would not have been
caught, this does suggest that the libstdc++ tests are too weak; tvector
does not try out even 1/10 of the vector class functionality. Tests that
at least call each method of vector (and the other STL classes) at least
once would be a great help. (Perhaps others already have something: the
ObjectSpace free tests seem too weak).
next reply other threads:[~1997-09-28 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-28 15:49 Joe Buck [this message]
1997-09-29 9:56 ` Mark Mitchell
[not found] <199709282248.PAA07344.cygnus.egcs@atrus.synopsys.com>
1997-09-29 9:40 ` Jason Merrill
1997-09-29 12:35 ` Jan Springer
1997-09-29 15:09 ` Joe Buck
1997-09-29 18:39 ` Jason Merrill
1997-09-29 14:02 Bob Sidebotham
1997-10-03 10:59 Mark Mitchell
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=199709282248.PAA07344@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
/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).