public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: stm@bigfoot.de To: gcc-gnats@gcc.gnu.org Subject: target/7456: #243 gcc2.96 - template problems Date: Wed, 31 Jul 2002 10:06:00 -0000 [thread overview] Message-ID: <20020731170335.14304.qmail@sources.redhat.com> (raw) >Number: 7456 >Category: target >Synopsis: #243 gcc2.96 - template problems >Confidential: no >Severity: serious >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Jul 31 10:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: stm@bigfoot.de >Release: gcc version 2.96 20000731 (Mandrake Linux 8.2 2.96-0.76mdk) >Organization: >Environment: Linux PC PIII >Description: Don't look at the usefullness of the code, its wrong anyway. But the compiler can not report the mistake here. bug.cc:10: Internal error #243. bug.cc:10: confused by earlier errors, bailing out (the mistake is of course in line 20/21.) >How-To-Repeat: gcc bug.cc >Fix: not a fix, but a workaround (problem may be to find the place where you made a mistake in the code you compile) - by correct use of template function (see comment in file), then it reports a normal compiler error - not using an array reference/pointer as parameter of the function definition produces also a normal compiler error >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="bug.cc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="bug.cc" CgpjbGFzcyBYCnsKcHVibGljOgogIHZvaWQgbWV0aG9kKCk7Cn07Cgp0ZW1wbGF0ZSA8aW50IEgs IGludCBXPiB2b2lkIGZ1bmN0aW9uKGludCAoJndtYXJrZXIpW0hdW1ddKQp7Cn07Cgp2b2lkIFg6 Om1ldGhvZCgpCnsKICBpbnQgaCA9IDIyOwogIGludCB3ID0gMTg7CgogIGludCBhcnJheVtoXVt3 XTsKCiAgLy9mdW5jdGlvbjwyMiwxOD4oYXJyYXkpOwogIGZ1bmN0aW9uKGFycmF5KTsKfQoK
reply other threads:[~2002-07-31 17:06 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=20020731170335.14304.qmail@sources.redhat.com \ --to=stm@bigfoot.de \ --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: 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).