public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: RE: c++/9942: Function Overload Resolution calls wrong function o n variable length parameter lists
Date: Wed, 05 Mar 2003 23:06:00 -0000	[thread overview]
Message-ID: <20030305230600.23830.qmail@sources.redhat.com> (raw)

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

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Steve Wadsworth <Steve_Wadsworth@portasystems.co.uk>
Cc: "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>,
   "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>
Subject: RE: c++/9942: Function Overload Resolution calls wrong function o
 n variable length parameter lists
Date: Wed, 5 Mar 2003 17:03:00 -0600 (CST)

 > Attached is sample code to exhibit this. 
 
 OK, here's a reduced example:
 ------------------------
 #include <stdarg.h>
 
 void f(int, va_list&)  ;   // only declared
 void f(int, ...)     {};   // defined
 
 int main () {
   char *p;
   f(1, p);         // should probably call second f()
 }
 ------------------------
 
 This compiles and links fine with 2.95, but not with 3.2.1. Will have to 
 check on that other system what happens with 3.3 and mainline.
 
 W.
 
 Here's the result:
 tmp/g> ~/bin/gcc-3.2.1/bin/c++ x.cc
 /tmp/ccOD0xO1.o: In function `main':
 /tmp/ccOD0xO1.o(.text+0x25): undefined reference to `f(int, char*&)'
 collect2: ld returned 1 exit status
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-03-05 23:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 23:06 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-05 18:06 Steve Wadsworth

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=20030305230600.23830.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --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).