From: Jim Blandy <jimb@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@cygnus.com
Subject: Re: More gdb-4.17.85 testresults
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <npaexm4p27.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <36E4A175.DEA4FA72@cygnus.com>
I'm not concerned with a warning-free build for 4.18. That is
something I would like to have for 4.19.
Based on the responses from the ANSI C wonks, I think you're going to
have to change the argument types in the prototypes. Glancing over
it, this doesn't look like a problem.
next prev parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9903039205.AA920520366.cygnus.gdb@cc.pmsc.com>
[not found] ` <npaexm4p27.fsf.cygnus.gdb@zwingli.cygnus.com>
1999-04-01 0:00 ` Andrew Cagney
1999-04-01 0:00 ` Andrew Cagney
1999-04-01 0:00 ` Jim Blandy [this message]
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` Todd Whitesel
1999-04-01 0:00 ` Mike Vermeulen
1999-04-01 0:00 rodneybrown
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=npaexm4p27.fsf@zwingli.cygnus.com \
--to=jimb@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=gdb@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