From: Zack Weinberg <zack@codesourcery.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: General search for symbols...
Date: Thu, 10 Apr 2003 09:37:00 -0000 [thread overview]
Message-ID: <87u1d6uda6.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <200304041712.h34HCnf03282@piper.synopsys.com> (Joe Buck's message of "Fri, 4 Apr 2003 09:12:49 -0800 (PST)")
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.)
zw
===================================================================
Index: gcc-3.4/changes.html
--- gcc-3.4/changes.html 6 Apr 2003 15:18:53 -0000 1.18
+++ gcc-3.4/changes.html 10 Apr 2003 05:33:19 -0000
@@ -22,6 +22,11 @@
<li>GCC no longer accepts the options <code>-fvolatile</code>,
<code>-fvolatile-global</code> and <code>-fvolatile-static</code>.
It is unlikely that they worked correctly in any 3.x release.</li>
+ <li>GCC no longer supports the use of <code><varargs.h></code>
+ and does not provide this header with the distribution. Use
+ <code><stdarg.h></code> instead. (This header is primarily
+ useful with traditional mode compilation, which feature was removed
+ in GCC 3.3.)
</ul>
<h2>General Optimizer Improvements</h2>
next prev parent reply other threads:[~2003-04-10 5:33 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 [this message]
2003-04-10 19:36 ` Mike Stump
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=87u1d6uda6.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.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).