From: Max Lawson <mlawson@drfmc.ceng.cea.fr>
To: egcs@cygnus.com
Subject: Continued: egcs-971201: testsuite results for i586-pc-linux-gnulibc1
Date: Tue, 02 Dec 1997 09:56:00 -0000 [thread overview]
Message-ID: <9712021644.AA20857@drfmc.ceng.cea.fr> (raw)
.. the typename5.C failure has left :-)
Nevertheless, programs I have that are heavily relying on templates still
make the system run out of memory depending on the optimization level. I'm
trying to narrow down the problem to a simple testcase, but :^( ..
Anyway, this is a _severe_ limitation for large programs :-(. or even
small programs... {:-((
For example, the following testcase quoted from "egcs-bugs/1997-Nov/0235.html"
still crash at compile time with the current 971201-snapshot on my box:
// --- test.cc ---
#include <iostream.h>
#include <list>
#include <algorithm>
using namespace std;
int main()
{
int daten [16] = { 1, 4, 4, 6, 1, 2, 2, 3, 6, 6, 6, 5, 7, 5, 4, 4};
list<int> menge;
copy (daten, daten+16, back_inserter(menge));
return 0;
}
// --- cc.tset ---
$g++ -Wall -O test.cc
test.cc: In function `int main()':
test.cc:10: virtual memory exhausted
This happens in the call to copy; this let's me wonder if this is not
related to non-trivial template instantiations of functions arguments.
That's my 0.00000000000000000000000000000000000000000002cts guess.
(Note that I use to (I have to) call the compiler with no warning flags
for my programs, therefore there is in my case no warning/optimization flags
combinations.)
Anyhow, thanx a lot for the job !-)
Best Regards, Max.
----------
libc.5.39 & ld.so.1.9.5 & binutils-2.8.1.0.15
./configure --enable-shared
BOOT_CFLAGS="-O6 -g"
----------
Test Run By lawson on Tue Dec 2 13:45:33 1997
Native configuration is i586-pc-linux-gnulibc1
=== gcc Summary ===
# of expected passes 4883
# of expected failures 5
# of unsupported tests 7
/tmp/egcs-971201/gcc/xgcc version egcs-2.90.20 971201 (gcc2-970802 experimental)
=== g++ tests ===
XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
XPASS: g++.mike/dyncast1.C Execution test
XPASS: g++.mike/dyncast2.C Execution test
=== g++ Summary ===
# of expected passes 3400
# of unexpected successes 3
# of expected failures 80
# of untested testcases 6
/tmp/egcs-971201/gcc/testsuite/../xgcc version egcs-2.90.20 971201 (gcc2-970802 experimental)
=== libio Summary ===
# of expected passes 40
=== libstdc++ Summary ===
# of expected passes 30
next reply other threads:[~1997-12-02 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-02 9:56 Max Lawson [this message]
[not found] <9712021644.AA20857.cygnus.egcs@drfmc.ceng.cea.fr>
1997-12-02 20:32 ` Jason Merrill
1997-12-02 18:13 ` Jeffrey A Law
1997-12-03 5:46 Max Lawson
1997-12-03 12:54 ` Jason Merrill
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=9712021644.AA20857@drfmc.ceng.cea.fr \
--to=mlawson@drfmc.ceng.cea.fr \
--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).