public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Martin Sebor <sebor@roguewave.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/2922: two-phase name lookup not working
Date: Thu, 24 May 2001 14:46:00 -0000	[thread overview]
Message-ID: <20010524214603.9765.qmail@sourceware.cygnus.com> (raw)

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

From: Martin Sebor <sebor@roguewave.com>
To: Jens.Maurer@gmx.net
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/2922: two-phase name lookup not working
Date: Thu, 24 May 2001 15:47:15 -0600

 Jens.Maurer@gmx.net wrote:
 > 
 > >Number:         2922
 > >Category:       c++
 > >Synopsis:       two-phase name lookup not working
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    unassigned
 > >State:          open
 > >Class:          wrong-code
 > >Submitter-Id:   net
 > >Arrival-Date:   Thu May 24 02:06:01 PDT 2001
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Jens Maurer
 > >Release:        gcc version 3.0 20010521 (prerelease)
 > >Organization:
 > >Environment:
 > Linux 2.2.4 with glibc 2.2.3
 > >Description:
 > The program below is supposed to output
 > f(char)
 > f(int)
 > f(char)
 > f(char)
 > 
 > according to 14.6p9.
 
 But take a look at issue 197 at
 
     http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/cwg_active.html#197
 
 Not that the issue makes gcc's behavior correct (f(char) should 
 apparently be called in all 4 cases).
 
 Regards
 Martin
 
 > 
 > gcc (all of 2.95.3, pre-3.0, and 3.1 20010518) outputs
 > f(int)
 > f(int)
 > f(int)
 > f(char)
 > >How-To-Repeat:
 > 
 > // example (slightly adapted) from 14.6p9
 > 
 > #include <iostream>
 > 
 > void f(char)
 > {
 >   std::cout << "f(char)" << std::endl;
 > }
 > 
 > template<class T>
 > void g(T t)
 > {
 >   f(1);        // not dependent
 >   f(t);        // dependent
 > }
 > 
 > void f(int)
 > {
 >   std::cout << "f(int)" << std::endl;
 > }
 > 
 > int main()
 > {
 >   g(2);    // f(char) followed by f(int)
 >   g('a');  // two f(char)
 > }
 > 
 > >Fix:
 > 
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:


             reply	other threads:[~2001-05-24 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-24 14:46 Martin Sebor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-24 15:56 Jens Maurer
2001-05-24  2:06 Jens.Maurer

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=20010524214603.9765.qmail@sourceware.cygnus.com \
    --to=sebor@roguewave.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).