public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c++/4095: Variable misspelled in gcc/cp/rtti.c Date: Thu, 23 Aug 2001 21:56:00 -0000 [thread overview] Message-ID: <20010824045601.25862.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/4095; it has been noted by GNATS. From: Andreas Jaeger <aj@suse.de> To: rkl@connect.org.uk Cc: gcc-gnats@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: c++/4095: Variable misspelled in gcc/cp/rtti.c Date: Fri, 24 Aug 2001 06:52:00 +0200 rkl@connect.org.uk writes: >>Number: 4095 >>Category: c++ >>Synopsis: Variable misspelled in gcc/cp/rtti.c [...] > >Description: > In line 1293 (create_pseudo_type_info() function), the > first param of va_arg() is spelled "app", which doesn't > exist as a variable. > >How-To-Repeat: > Compile without ANSI_PROTOTYPES defined - I did this by > building with a K&R C compiler. > >Fix: > Line 1293 should read: > > ident = va_arg (ap, int); Here's a patch. Ok to commit to the trunk? Or should we remove this ANSI_PROTOTYPES stuff since cp will be compiled with GCC? Andreas 2001-08-24 Andreas Jaeger <aj@suse.de>, rkl@connect.org.uk * cp/rtti.c (VPARAMS): Fix parameter. ============================================================ Index: gcc/cp/rtti.c --- gcc/cp/rtti.c 2001/08/14 23:51:27 1.121 +++ gcc/cp/rtti.c 2001/08/24 04:51:35 @@ -1170,7 +1170,7 @@ VA_START (ap, ident); #ifndef ANSI_PROTOTYPES real_name = va_arg (ap, char const *); - ident = va_arg (app, int); + ident = va_arg (ap, int); #endif /* Generate the pseudo type name. */ -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj
next reply other threads:[~2001-08-23 21:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-08-23 21:56 Andreas Jaeger [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-09-29 11:47 rodrigc 2001-08-24 12:56 Zack Weinberg 2001-08-24 9:46 Mark Mitchell 2001-08-23 7:36 rkl
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=20010824045601.25862.qmail@sourceware.cygnus.com \ --to=aj@suse.de \ --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: 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).