From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Modernize solaris threads support.
Date: Mon, 16 Feb 2009 19:35:00 -0000 [thread overview]
Message-ID: <uhc2uw64a.fsf@gnu.org> (raw)
In-Reply-To: <200902160549.49108.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Mon, 16 Feb 2009 05:49:48 +0000
>
> Started out as getting rid of a couple of deprecated_xfer_memory instances...
> * Adds a `this' target_ops pointer to a few more target_ops callbacks,
> so we get rid of a bunch of things like this, by instead calling
> the target beneath:
>
> - if (target_has_execution)
> - procfs_ops.to_fetch_registers (regcache, -1);
> - else
> - orig_core_ops.to_fetch_registers (regcache, -1);
I don't mind doing this, but...
> Index: src/gdb/go32-nat.c
> ===================================================================
> --- src.orig/gdb/go32-nat.c 2009-02-16 00:20:30.000000000 +0000
> +++ src/gdb/go32-nat.c 2009-02-16 03:26:06.000000000 +0000
> @@ -169,11 +169,7 @@ static void go32_open (char *name, int f
> static void go32_close (int quitting);
> static void go32_attach (char *args, int from_tty);
> static void go32_detach (char *args, int from_tty);
> -static void go32_resume (ptid_t ptid, int step,
> - enum target_signal siggnal);
> -static void go32_fetch_registers (struct regcache *, int regno);
> static void store_register (const struct regcache *, int regno);
> -static void go32_store_registers (struct regcache *, int regno);
Why did you need to remove these prototypes while at that?
Also, the argument you added is unused inside these functions.
Shouldn't we do something to shut up GCC warnings about them?
Other than that, the changes to go32-nat.c are approved.
Thanks.
next prev parent reply other threads:[~2009-02-16 19:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 8:57 Pedro Alves
2009-02-16 19:35 ` Eli Zaretskii [this message]
2009-02-16 20:45 ` Pedro Alves
2009-02-16 20:50 ` Eli Zaretskii
2009-02-17 0:07 ` Pedro Alves
2009-02-17 4:12 ` Eli Zaretskii
2009-02-17 13:30 ` Pedro Alves
2009-02-17 19:20 ` Eli Zaretskii
2009-02-17 20:01 ` Pedro Alves
2009-02-17 20:28 ` Tom Tromey
2009-02-17 20:50 ` Eli Zaretskii
2009-02-17 21:12 ` Tom Tromey
2009-02-18 2:06 ` Stan Shebs
2009-02-18 10:13 ` Eli Zaretskii
2009-02-18 14:47 ` Mark Kettenis
2009-02-18 19:50 ` Eli Zaretskii
2009-02-23 0:49 ` Pedro Alves
2009-02-23 1:22 ` Pedro Alves
2009-02-23 20:09 ` Pedro Alves
2009-02-24 14:48 ` Pierre Muller
2009-02-24 14:52 ` Pedro Alves
2009-02-24 15:04 ` Pierre Muller
2009-02-24 15:31 ` Pedro Alves
2009-02-24 15:58 ` [Commit] obvious: fix compilation failure for windows-nat.c Pierre Muller
2009-07-20 12:07 ` Restore GNU/Hurd functionality (was: Modernize solaris threads support.) Thomas Schwinge
2009-07-20 13:02 ` Pedro Alves
2009-07-20 15:08 ` Restore GNU/Hurd functionality Thomas Schwinge
2009-07-20 17:33 ` Pedro Alves
2009-02-26 19:45 ` Modernize solaris threads support David Daney
2009-02-27 18:22 ` Pedro Alves
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=uhc2uw64a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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