Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: toddpw@wrs.com (Todd Whitesel)
To: ac131313@cygnus.com (Andrew Cagney)
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: <199903090524.VAA25575@alabama.wrs.com> (raw)
In-Reply-To: <36E4A175.DEA4FA72@cygnus.com>

> > cc: "../../gdb-4.17.85/gdb/remote.c", line 693: \
> >     error 1711: Inconsistent parameter list declaration for "pack_hex_byte".
> 
> This one puzzles me.  Looking in remote.c I see:
> 
>     static char *pack_hex_byte PARAMS ((char *pkt, unsigned char byte));
> 
> and then:
> 
>     static char *
>     pack_hex_byte (pkt, byte)
>          char *pkt;
>          unsigned char byte;
>     {
> 
>Is this error because HP's compiler doesn't like the `unsigned char' parameter?

Yes, in both cases. This is a pedanticism of the HP compiler; it considers
the prototype to have ANSI argument conventions (char and unsigned char
really are only 8 bits) but it considers the definition to have K&R argument
conventions (char and unsigned char are implicitly promoted to int).

Most compilers recognize this case and accept it as a K&R->ANSI transition
tool, but the HP/UX compiler insists that the two prototypes are not the
same and rejects it.

Solutions:
	- widen the chars to ints
	- move to ANSI prototypes
	- disable PARAMS() on that host until ANSIfication proceeds

-- 
Todd Whitesel
toddpw @ wrs.com


  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   ` Mike Vermeulen
1999-04-01  0:00   ` Stan Shebs
1999-04-01  0:00   ` Todd Whitesel [this message]
1999-04-01  0:00   ` Jim Blandy
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=199903090524.VAA25575@alabama.wrs.com \
    --to=toddpw@wrs.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