public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: schwab@suse.de To: gcc-gnats@gcc.gnu.org Cc: kkaempf@suse.de, pthomas@suse.de Subject: c++/7581: ICE in grokdeclarator Date: Mon, 12 Aug 2002 16:16:00 -0000 [thread overview] Message-ID: <20020812220041.30884.qmail@sources.redhat.com> (raw) >Number: 7581 >Category: c++ >Synopsis: ICE in grokdeclarator >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Mon Aug 12 15:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: schwab@suse.de >Release: 3.2 20020729 (prerelease) (SuSE Linux) >Organization: >Environment: System: Linux sykes 2.4.18-SMP #1 SMP Thu May 16 09:03:14 UTC 2002 ia64 unknown unknown GNU/Linux Architecture: ia64 host: ia64-suse-linux-gnu build: ia64-suse-linux-gnu target: ia64-suse-linux-gnu configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --enable-languages=c,c++,f77,objc,java,ada --enable-libgcj --with-gxx-include-dir=/usr/include/g++ --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit ia64-suse-linux >Description: The attached (invalid) source causes an ICE in grokdeclarator. >How-To-Repeat: $ g++ -O2 -g -Wall -c -o badcode.o badcode.cc badcode.cc: In function `std::string badcode(const std::list<std::string, std::allocator<std::string> >&)': badcode.cc:11: `template<class _Category, class _Tp, class _Distance, class _Pointer, class _Reference> struct std::iterator' as declarator Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/x-c++src; name="badcode.cc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="badcode.cc" I2luY2x1ZGUgPHN0cmluZz4KI2luY2x1ZGUgPGxpc3Q+CnVzaW5nIG5hbWVzcGFjZSBzdGQ7Cgpz dHJpbmcgYmFkY29kZSAoY29uc3QgbGlzdDxzdHJpbmc+ICZkYXRhKQp7CiAgaWYgKCFkYXRhLnNp emUgKCkpCiAgICByZXR1cm4gIiI7CgogIHN0cmluZyByZXQ7CiAgZm9yIChsaXN0PHN0cmluZz4m OjppdGVyYXRvciBwb3MgPSBkYXRhLmJlZ2luICgpOyBwb3MgPCBkYXRhLmVuZCAoKTsgcG9zKysp CiAgICB7CiAgICAgIGlmICghcmV0LmVtcHR5KCkpCglyZXQgKz0gJ1xuJzsKICAgICAgcmV0ICs9 ICpwb3M7CiAgICB9CiAgcmV0dXJuIHJldDsKfQoKaW50Cm1haW4gKGludCBhcmdjLCBjaGFyICoq YXJndikKewogIHJldHVybiAwOwp9Cg==
next reply other threads:[~2002-08-12 22:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-12 16:16 schwab [this message] 2002-09-13 16:05 nathan 2002-10-16 12:45 mmitchel
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=20020812220041.30884.qmail@sources.redhat.com \ --to=schwab@suse.de \ --cc=gcc-gnats@gcc.gnu.org \ --cc=kkaempf@suse.de \ --cc=pthomas@suse.de \ /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: linkBe 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).