From: "Philippe De Muyter" <phdm@macqel.be>
To: ghazi@caip.rutgers.edu (Kaveh R. Ghazi)
Cc: bothner@cygnus.com, egcs@cygnus.com, law@cygnus.com
Subject: Re: egcs, does gcc fixincludes etc guarantee a stdlib.h exists?
Date: Tue, 14 Apr 1998 07:45:00 -0000 [thread overview]
Message-ID: <199804141445.QAA02737@mail.macqel.be> (raw)
In-Reply-To: <199804141433.KAA28154@caip.rutgers.edu>
> I considered doing that, but I wasn't completely sure defining
> that macro unconditionally in libgcc2.c or frame.c was a good idea. Are
> we guaranteed that defining __USE_FIXED_PROTOTYPES__ is safe for all
> platforms? (I don't know, I'm asking.) If it is safe, then why does the
> wrapper exist at all? ...
IIRC there are some functions for which the generated prototype is wrong on
some platforms (I do not remember which functions), but if you only want to get
the prototype for malloc then it is safe to define __USE_FIXED_PROTOTYPES__.
next prev parent reply other threads:[~1998-04-14 7:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-14 9:37 Kaveh R. Ghazi
1998-04-14 7:45 ` Philippe De Muyter [this message]
1998-04-16 16:34 ` Jim Wilson
1998-04-16 18:39 ` Jeffrey A Law
1998-04-17 2:23 ` Philippe De Muyter
1998-04-17 14:49 ` Jim Wilson
1998-04-20 4:16 ` Philippe De Muyter
1998-04-17 14:42 ` Philippe De Muyter
1998-04-20 22:16 ` Jim Wilson
1998-04-21 13:29 ` Philippe De Muyter
1998-04-21 17:38 ` Jim Wilson
-- strict thread matches above, loose matches on Subject: below --
1998-04-17 8:41 Kaveh R. Ghazi
1998-04-13 12:29 Kaveh R. Ghazi
1998-04-14 2:02 ` Philippe De Muyter
1998-04-16 15:31 ` Jim Wilson
1998-03-27 15:18 Kaveh R. Ghazi
1998-03-28 19:24 ` Philippe De Muyter
1998-03-29 5:14 ` Manfred Hollstein
1998-03-31 0:46 ` Manfred Hollstein
1998-03-31 0:46 ` Jeffrey A Law
1998-04-02 11:32 ` Per Bothner
1998-04-02 9:35 ` Jeffrey A Law
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=199804141445.QAA02737@mail.macqel.be \
--to=phdm@macqel.be \
--cc=bothner@cygnus.com \
--cc=egcs@cygnus.com \
--cc=ghazi@caip.rutgers.edu \
--cc=law@cygnus.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).