public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Leick Robinson <leick.robinson@motorola.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7686: template compilation failure on unused method
Date: Fri, 23 Aug 2002 08:46:00 -0000	[thread overview]
Message-ID: <20020823152602.32529.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/7686; it has been noted by GNATS.

From: Leick Robinson <leick.robinson@motorola.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/7686: template compilation failure on unused method
Date: Fri, 23 Aug 2002 10:17:33 -0500

 --------------71CDC3598563AC3C410BB7D1
 Content-Type: text/plain; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 Gabriel,
 
 I'm not sure I fully understand your response.  I was hoping you could
 clarify it for me.
 
 Do you mean that it was a bug in 2.95.2, that it should have instantiated
 the declarations (and thus, failed to compile)?
 And, further, that 3.0.4 is correct in its failure to compile?
 
 I'm not sure what a "regression from gcc-3.0.4" means (as stated in the
 Audit Trail).
 
 Leick
 
 
 Gabriel Dos Reis wrote:
 
 > leick.robinson@motorola.com writes:
 >
 > | This assumes that the rule for an uninstantiated member
 > | function extends to its declaration.  I am not certain
 > | whether the C++ standard is clear on this point.
 >
 > You're right:  This is a bug in g++, it should have instantiated the
 > *declarations* of the member functions.  I'll mark it as a regression.
 >
 > Thanks,
 >
 > -- Gaby
 
 --
  ____________________________________________________________________
 |  Leick Robinson --> "bRoken siLicon"                               |
 |  Manager, PowerPC Core Modeling Team                               |
 |                                                                    |
 |  Phone: (512) 996-4948                          \O/   BE OF        |
 |  Pager: (512) 1-888-561-6477                     |   GOOD    \ /   |
 |  Email: leick.robinson@motorola.com             / \   CHEER!  |    |
 |                    PowerPC System Enablement                 /O\   |
 |                          Motorola-Austin                           |
 |                                                                    |
 |  "There exists a passion for comprehension, just as there exists   |
 |  a passion for music.  That passion is rather common in children,  |
 |  but gets lost in most people later on."  -- A. Einstein, 1950     |
 |____________________________________________________________________|
 
 
 
 --------------71CDC3598563AC3C410BB7D1
 Content-Type: text/html; charset=us-ascii
 Content-Transfer-Encoding: 7bit
 
 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 <html>
 Gabriel,
 <p>I'm not sure I fully understand your response.&nbsp; I was hoping you
 could clarify it for me.
 <p>Do you mean that it was a bug in 2.95.2, that it should have instantiated
 the declarations (and thus, failed to compile)?
 <br>And, further, that 3.0.4 is correct in its failure to compile?
 <p>I'm not sure what a "regression from gcc-3.0.4" means (as stated in
 the Audit Trail).
 <p>Leick
 <br>&nbsp;
 <p>Gabriel Dos Reis wrote:
 <blockquote TYPE=CITE>leick.robinson@motorola.com writes:
 <p>| This assumes that the rule for an uninstantiated member
 <br>| function extends to its declaration.&nbsp; I am not certain
 <br>| whether the C++ standard is clear on this point.
 <p>You're right:&nbsp; This is a bug in g++, it should have instantiated
 the
 <br>*declarations* of the member functions.&nbsp; I'll mark it as a regression.
 <p>Thanks,
 <p>-- Gaby</blockquote>
 
 <pre>--&nbsp;
 &nbsp;____________________________________________________________________
 |&nbsp; Leick Robinson --> "bRoken siLicon"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
 |&nbsp; Manager, PowerPC Core Modeling Team&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
 |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
 |&nbsp; Phone: (512) 996-4948&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \O/&nbsp;&nbsp; BE OF&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
 |&nbsp; Pager: (512) 1-888-561-6477&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp; GOOD&nbsp;&nbsp;&nbsp; \ /&nbsp;&nbsp; |
 |&nbsp; Email: leick.robinson@motorola.com&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; / \&nbsp;&nbsp; CHEER!&nbsp; |&nbsp;&nbsp;&nbsp; |
 |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PowerPC System Enablement&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /O\&nbsp;&nbsp; |
 |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Motorola-Austin&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
 |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
 |&nbsp; "There exists a passion for comprehension, just as there exists&nbsp;&nbsp; |
 |&nbsp; a passion for music.&nbsp; That passion is rather common in children,&nbsp; |
 |&nbsp; but gets lost in most people later on."&nbsp; -- A. Einstein, 1950&nbsp;&nbsp;&nbsp;&nbsp; |
 |____________________________________________________________________|</pre>
 &nbsp;</html>
 
 --------------71CDC3598563AC3C410BB7D1--
 


             reply	other threads:[~2002-08-23 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-23  8:46 Leick Robinson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-16 10:21 mmitchel
2002-08-23  9:36 Gabriel Dos Reis
2002-08-22 16:56 Gabriel Dos Reis
2002-08-22 16:26 gdr
2002-08-22 13:26 leick.robinson

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=20020823152602.32529.qmail@sources.redhat.com \
    --to=leick.robinson@motorola.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).