From: Jeffrey A Law <law@hurl.cygnus.com>
To: egcs@cygnus.com
Subject: Re: A prototype patch for tree.h/tree.def/calls.c
Date: Tue, 19 Aug 1997 19:00:07 -0000 [thread overview]
Message-ID: <m0x0seU-0004ecC@ocean.lucon.org> (raw)
Message-ID: <19970819190007.ZJK2lZf9UXflSStzlaPuX1gGnRFARK7gCVzTlsFGETM@z> (raw)
In-Reply-To: A prototype patch for tree.h/tree.def/calls.c
In message <m0x0r16-0004edC@ocean.lucon.org>you write:
> >
> > 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.
Please disable them for the patch.
> 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.
NO! You simply can't change from size_t to unsigned, that's
just plain wrong.
Seems to me the right way to do this is with autoconf.
> 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.
Then they're not likely to go in anytime soon. I don't have the
time to spend reformatting all your changes.
> 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
I had a feeling you'd done something like this -- let's punt this
for now until we can come up with something better.
So, it seems to me you need to do 3 things:
* #if0 the xmalloc and friends prototypes.
* Don't mess with the enum rtx_code and enum tree_code stuff
right now.
* Do some minor formatting.
We're not talking about a lot of work that you'd need to do to
get your patches installed immediately.
Jeff
next reply other threads:[~1997-08-19 19:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-19 19:00 Jeffrey A Law [this message]
1997-08-19 19:00 ` Unique SMTP From header? Dan A. Dickey
1997-08-19 19:00 ` A prototype patch for tree.h/tree.def/calls.c Jeffrey A Law
1997-08-19 19:00 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
1997-09-04 11:27 Some Haifa scheduler bugs meissner
[not found] <Pine.SOL.3.90.970826141030.2901K-100000@maigret.informatik.rwth-aachen.de>
1997-09-01 20:42 ` Jeffrey A Law
[not found] <Pine.SOL.3.90.970826140826.2901J-100000@maigret.informatik.rwth-aachen.de>
1997-09-01 20:33 ` Jeffrey A Law
1997-09-03 9:30 ` Bernd Schmidt
1997-09-03 9:37 ` Jeffrey A Law
1997-09-03 9:44 ` Bernd Schmidt
1997-09-03 10:07 ` Jeffrey A Law
1997-09-05 7:15 ` Bernd Schmidt
1997-09-05 7:55 ` Jeffrey A Law
1997-09-05 8:33 ` Ian Lance Taylor
1997-09-03 11:58 ` Jim Wilson
1997-09-03 11:39 ` Paul Koning
1997-09-03 11:50 ` David Edelsohn
1997-09-03 13:13 ` Richard Henderson
1997-09-03 13:19 ` Jeffrey A Law
1997-09-04 9:33 ` Craig Burley
1997-09-04 11:12 ` Jeffrey A Law
1997-09-04 11:33 ` David S. Miller
1997-09-04 14:38 ` David Edelsohn
1997-08-26 14:34 Bernd Schmidt
1997-08-22 13:53 Building of generated parser files Andreas Schwab
1997-08-22 15:02 ` Some Haifa scheduler bugs Jeffrey A Law
1997-08-22 15:24 ` Jeffrey A Law
1997-08-22 10:48 Building of generated parser files Niklas Hallqvist
1997-08-22 13:28 ` Some Haifa scheduler bugs Bernd Schmidt
1997-08-21 16:51 Problems on PowerPC David Edelsohn
1997-08-21 17:43 ` Some Haifa scheduler bugs Jeffrey A Law
1997-08-21 15:20 egcs repository Joel Sherrill
1997-08-21 15:47 ` Some Haifa scheduler bugs Bernd Schmidt
1997-08-19 17:54 Jeffrey A Law
1997-08-19 7:36 egcs: A new compiler project to merge the existing GCC forks (fwd) Robert Wilhelm
1997-08-19 9:34 ` Some Haifa scheduler bugs Bernd Schmidt
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=m0x0seU-0004ecC@ocean.lucon.org \
--to=law@hurl.cygnus.com \
--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).