public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: wolfgang.bangerth@iwr.uni-heidelberg.de To: gcc-gnats@gcc.gnu.org Subject: c++/2863: gcc accepts invalid explicit specialization syntax Date: Fri, 18 May 2001 01:46:00 -0000 [thread overview] Message-ID: <20010518084243.22971.qmail@sourceware.cygnus.com> (raw) >Number: 2863 >Category: c++ >Synopsis: gcc accepts invalid explicit specialization syntax >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: accepts-illegal >Submitter-Id: net >Arrival-Date: Fri May 18 01:46:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Wolfgang Bangerth >Release: unknown-1.0 >Organization: >Environment: gcc 2.95, gcc cvs of May 05 >Description: As a follow-up to the last report, talking about explicit instantiations: gcc also allows explicit specializations with wrong arguments. This is somewhat more critical, as the compiler thereby looses the ability to warn you about the then necessarily unused arguments. Regards Wolfgang >How-To-Repeat: -----/gcc-bugs> cat a.cc struct X { template <int dim> void f(int=0); }; template <> void X::f<1> () {}; -----/gcc-bugs> ~/Config/gcc-ss-sun/bin/gcc -W -Wall -ansi -c a.cc -o /dev/null -----/gcc-bugs> ~/Config/gcc-ss-sun/bin/gcc -v Reading specs from /home/atlas2/wolf/Config/gcc-ss-sun/bin/../lib/gcc-lib/sparc-sun-solaris2.7/3.0/specs Configured with: ../gcc/configure --prefix=/home/people/wolf/Config/gcc-ss-sun --with-gnu-as --with-as=/usr/local/bin/as --with-gnu-ld --with-ld=/usr/local/bin/ld Thread model: posix gcc version 3.0 20010514 (prerelease) >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-05-18 1:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-05-18 1:46 wolfgang.bangerth [this message] 2002-06-14 9:51 lerdsuwa 2002-07-17 7:27 lerdsuwa
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=20010518084243.22971.qmail@sourceware.cygnus.com \ --to=wolfgang.bangerth@iwr.uni-heidelberg.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).