public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/17232] classes and class template specializations treated differently w.r.t. core issue #337
Date: Sun, 29 Aug 2004 18:42:00 -0000	[thread overview]
Message-ID: <20040829184254.29677.qmail@sourceware.org> (raw)
In-Reply-To: <20040829175551.17232.cludwig@cdc.informatik.tu-darmstadt.de>


------- Additional Comments From bangerth at dealii dot org  2004-08-29 18:42 -------
I don't presently have the time to figure things out, but here are 
a few data points: 
  gcc2.95, 3.2.3, and 3.3.4 return 1 
  gcc3.4.1, gcc mainline, and icc8 return 0 
 
Note also that the declaration 
  int g(T (*)[1]) 
is taking an argument of type pointer to array of T. However, as the 
types you use are abstract, there can't be any arrays of these types 
and this declaration should probably never match. 
 
That doesn't invalidate your point, though, that the compiler should 
probably treat template instances and non-template classes equivalently. 
 
W. 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17232


  parent reply	other threads:[~2004-08-29 18:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-29 17:55 [Bug c++/17232] New: " cludwig at cdc dot informatik dot tu-darmstadt dot de
2004-08-29 17:58 ` [Bug c++/17232] " cludwig at cdc dot informatik dot tu-darmstadt dot de
2004-08-29 18:42 ` bangerth at dealii dot org [this message]
2004-08-29 18:57 ` cludwig at cdc dot informatik dot tu-darmstadt dot de
2004-08-30 12:30 ` giovannibajo at libero dot it
2004-08-30 13:22 ` cludwig at cdc dot informatik dot tu-darmstadt dot de
2004-08-30 14:47 ` giovannibajo at libero dot it
2004-08-30 16:05 ` bangerth at dealii dot org
2004-08-30 16:56 ` cludwig at cdc dot informatik dot tu-darmstadt dot de
2004-08-30 20:10 ` giovannibajo at libero dot it
2004-08-30 20:56 ` bangerth at dealii dot org
2004-08-30 22:12 ` jason at redhat dot com
2004-08-30 23:15 ` giovannibajo at libero dot it
2004-09-06  7:03 ` cludwig at cdc dot informatik dot tu-darmstadt dot de
2004-09-06 13:40 ` giovannibajo at libero dot it
2004-09-06 13:43 ` giovannibajo at libero dot it
2004-09-27 12:02 ` giovannibajo at libero dot it
     [not found] <bug-17232-4@http.gcc.gnu.org/bugzilla/>
2013-02-27 18:03 ` jason at gcc dot gnu.org
2013-03-17  2:37 ` jason at gcc dot gnu.org
2013-03-17 20:32 ` jason at gcc dot gnu.org
2013-03-23 17:08 ` jason at gcc dot gnu.org
2013-04-09  1:30 ` jason at gcc dot gnu.org
2014-04-22 11:37 ` jakub at gcc dot gnu.org
2014-07-16 13:31 ` jakub at gcc dot gnu.org

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=20040829184254.29677.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).