From: H.J. Lu <hjl@lucon.org>
To: egcs@cygnus.com
Subject: Re: A prototype patch for tree.h/tree.def/calls.c
Date: Tue, 19 Aug 1997 17:54:31 -0000 [thread overview]
Message-ID: <m0x0r16-0004edC@ocean.lucon.org> (raw)
In-Reply-To: 3130.872004634@hurl.cygnus.com
>
> In message <m0x0opG-0004edC@ocean.lucon.org>you write:
> > I have some problem s with my emails for the past few days. I may
> > have lost some. I only remember your comments on BUFSIZ being a macro,
> > which turned out ok. What else?
> Relatively minor stuff.
>
> For this pass #if 0 the prototypes for xmalloc and related funtions;
> once the bulk of the prototypes are in, please submit a separate
> patch to enable prototyping of xmalloc and related functions.
On my machine, they are enabled.
>
> This should help deal with the varying prototypes and lack of
> proper casts throughout the gcc sources.
>
> Also, the prototypes are wrong, you changed an argument from a
> "size_t" to "unsigned". On some systems, they're different
> sizes!
>
That is exactly the problem with size_t. How can you be
sure size_t is available on all systems when xmalloc ()
is used? many xmalloc () in gcc use unsigned. I think
it makes some senses.
>
>
> Other prototypes in rtl.h (and other locations) try to get the PROTOs
> to line up in a nice column. Can you line them up? It will certainly
> make them easier to read later. Seems like a nit, but it really
> makes stuff easier to read.
>
I have spent weeks on it. I am afraid I may make some
stupid mistakes if I try to reformat it. After all,
those prototypes are mainly for compiler. Please feel
free to reformat it. Thanks.
>
> > The reason of
> > odd rtl.def patch is the prototyping config.h may require
> > enum etx_code before rtl.h is included.
> I don't understand this.
>
> If config.h requires enum rtx_code before rtl.h is included, how
> does this change help?
>
> I would punt this issue for this round too. We can return to it after
> we've got the bulk of the other prototype stuff installed.
Here is what I have in my i386.h:
#define NEED_enum_rtx_code
#include "rtl.def"
#undef NEED_enum_rtx_code
#define NEED_enum_machine_mode
#include "machmode.def"
#undef NEED_enum_machine_mode
.....
extern int ix86_expand_binary_operator
PROTO ((enum rtx_code, enum machine_mode, struct rtx_def *[]));
.....
As I said, gcc was not designed with prototyping in mind.
H.J.
next reply other threads:[~1997-08-19 17:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-19 17:54 H.J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-08-19 21:22 Ian Haggard
1997-08-19 19:24 Ugly *.def in gcc H.J. Lu
1997-08-19 19:45 ` A prototype patch for tree.h/tree.def/calls.c Jeffrey A Law
1997-08-19 19:12 H.J. Lu
1997-08-19 19:00 Some Haifa scheduler bugs Jeffrey A Law
1997-08-19 19:00 ` A prototype patch for tree.h/tree.def/calls.c H.J. Lu
1997-08-19 19:00 ` Jeffrey A Law
1997-08-19 19:00 H.J. Lu
1997-08-19 19:00 ` Jeffrey A Law
1997-08-19 17:52 John Carr
1997-08-19 17:43 D.V. Henkel-Wallace
1997-08-19 16:06 egcs: A new compiler project to merge the existing GCC forks H.J. Lu
1997-08-19 16:06 ` A prototype patch for tree.h/tree.def/calls.c Jeffrey A Law
1997-08-19 13:19 H.J. Lu
1997-08-19 3:52 egcs: A new compiler project to merge the existing GCC forks (fwd) H.J. Lu
1997-08-19 5:08 ` A prototype patch for tree.h/tree.def/calls.c Jeffrey A Law
1997-08-18 23:56 H.J. Lu
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=m0x0r16-0004edC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@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).