From: Mike Stump <mrs@apple.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: Joe Buck <jbuck@synopsys.com>, gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: General search for symbols...
Date: Thu, 10 Apr 2003 19:36:00 -0000 [thread overview]
Message-ID: <61A218EB-6B82-11D7-8AD9-003065A77310@apple.com> (raw)
In-Reply-To: <87u1d6uda6.fsf@egil.codesourcery.com>
On Wednesday, April 9, 2003, at 10:33 PM, Zack Weinberg wrote:
> Joe Buck <jbuck@synopsys.com> writes:
>
>> Zack writes:
>>> Note that as of 3.3 GCC no longer supports <varargs.h>, although
>>> there
>>> are still vestiges of the old code for it.
>>
>> We should have a mention of that (together with any other deprecated
>> features not already mentioned) on
>>
>> http://gcc.gnu.org/gcc-3.3/changes.html
>
> Done. (I misspoke; it was only removed in 3.4, although it doesn't
> make a lot of sense to use <varargs.h> with 3.3 which dropped
> -traditional.)
Ok, I am confused then. What does the varargs.h header in 3.3 do then:
#ifndef _VARARGS_H
#define _VARARGS_H
#error "GCC no longer implements <varargs.h>."
#error "Revise your code to use <stdarg.h>."
#endif
?
next prev parent reply other threads:[~2003-04-10 18:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 14:10 Stephen Biggs
2003-04-02 16:22 ` Hans-Peter Nilsson
2003-04-03 7:18 ` Stephen Biggs
2003-04-04 2:13 ` Hans-Peter Nilsson
2003-04-04 9:35 ` Zack Weinberg
2003-04-04 18:51 ` Joe Buck
2003-04-10 9:37 ` Zack Weinberg
2003-04-10 19:36 ` Mike Stump [this message]
2003-04-10 20:03 ` Zack Weinberg
2003-04-10 20:12 ` Mike Stump
2003-04-09 8:43 ` Stephen Biggs
2003-04-02 15:07 Ilia Dyatchkov
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=61A218EB-6B82-11D7-8AD9-003065A77310@apple.com \
--to=mrs@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.com \
--cc=zack@codesourcery.com \
/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).