Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@cygnus.com>
To: Paul Hilfinger <hilfingr@gnat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFC: Killing some warnings
Date: Mon, 12 Feb 2001 14:55:00 -0000	[thread overview]
Message-ID: <1010212225533.ZM10647@ocotillo.lan> (raw)
In-Reply-To: <20010211075957.3E9F434D80@nile.gnat.com>

On Feb 11,  2:59am, Paul Hilfinger wrote:

> 	* hpux-thread.c (save_inferior_pid): Change call to make_cleanup
> 	to make arguments conform.
> 	(restore_inferior_pid): Change signature to that expected by
> 	make_cleanup.
[...]
> *************** static struct target_ops hpux_thread_ops
> *** 102,114 ****
>   static struct cleanup *
>   save_inferior_pid (void)
>   {
> !   return make_cleanup (restore_inferior_pid, inferior_pid);
>   }
>   
>   static void
> ! restore_inferior_pid (int pid)
>   {
> !   inferior_pid = pid;
>   }
>   \f
>   static int find_active_thread (void);
> --- 102,114 ----
>   static struct cleanup *
>   save_inferior_pid (void)
>   {
> !   return make_cleanup (restore_inferior_pid, (void*) inferior_pid);
>   }
>   
>   static void
> ! restore_inferior_pid (void* pid)
>   {
> !   inferior_pid = (int) pid;
>   }
>   \f
>   static int find_active_thread (void);

Personally, I'd prefer to see these changed to avoid the casts to (void *)
and (int).  See the implementation in lin-thread.c (and also elsewhere)
for an example.

(If we ever get around to merging my pid/tid/lwp megapatch, these are
cleaned up everywhere.  I.e, there is one implementation that all files
which need to do this sort of thing use.)

Kevin


  reply	other threads:[~2001-02-12 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-11  0:00 Paul Hilfinger
2001-02-12 14:55 ` Kevin Buettner [this message]
2001-02-13 14:28   ` Andrew Cagney

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=1010212225533.ZM10647@ocotillo.lan \
    --to=kevinb@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hilfingr@gnat.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