This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
target/7456: #243 gcc2.96 - template problems
- From: stm at bigfoot dot de
- To: gcc-gnats at gcc dot gnu dot org
- Date: 31 Jul 2002 17:03:35 -0000
- Subject: target/7456: #243 gcc2.96 - template problems
- Reply-to: stm at bigfoot dot de
>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