public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ldelana@libero.it
To: gcc-gnats@gcc.gnu.org
Cc: ldelana@libero.it
Subject: c++/6716: g++ loops itself and fill ram during compiling
Date: Sat, 18 May 2002 05:26:00 -0000 [thread overview]
Message-ID: <20020518122335.E859BE2CD2@alpha> (raw)
>Number: 6716
>Category: c++
>Synopsis: loop and fill ram during compiling
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Sat May 18 05:26:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Lorenzo Delana
>Release: 3.1 20020508 (prerelease)
>Organization:
none
>Environment:
System: Linux alpha 2.4.18 #1 Thu May 16 08:34:19 CEST 2002 i686 unknown
Architecture: i686
AMDK7(1.1Ghz), Linux-2.4.18+cryptoapi, athlon, glibc-{linuxthreads}-2.2.5
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3.1-20020508/configure --prefix=/usr/gcc-3.1 --enable-shared --enable-languages=c,c++,objc --enable-threads : (reconfigured) ../gcc-3.1-20020508/configure --with-gcc-version-trigger=/usr/src/gcc-3.1-20020508/gcc/version.c --host=i686-pc-linux-gnu --prefix=/usr/gcc-3.1 --enable-shared --enable-languages=c,c++,objc,f77 --enable-threads
>Description:
try with g++ -c on this simple wrong code:
// --- cut here --
#include <iostream>
#include <set>
using namespace std;
template<class T>
class X
{
public:
X() {}
virtual ~X() { }
bool operator()( T*, T* ) const { return true; }
protected:
T* x;
set< X<T>*, X<T> > aset; // <-- THIS IS THE WRONG CODE X<T> for less-than op
};
class Y : public X<int>
{
public:
};
// --- cut here --
>How-To-Repeat:
g++ -c <code.cxx>
>Fix:
check why loop on set STL _Compare using class itself for less-than op
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2002-05-18 12:26 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=20020518122335.E859BE2CD2@alpha \
--to=ldelana@libero.it \
--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).