From: Andrew Cagney <ac131313@cygnus.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: Paul Hilfinger <hilfingr@gnat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFC: Killing some warnings
Date: Tue, 13 Feb 2001 14:28:00 -0000 [thread overview]
Message-ID: <3A8983CD.8AC11A4B@cygnus.com> (raw)
In-Reply-To: <1010212225533.ZM10647@ocotillo.lan>
> 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.
That is correct - you can't robustly cast (int) <-> (void*) on some
architectures. Plenty of examples of how to handle this cleanly. See
sol-thread.c:restore_inferior_thread() for instance.
> (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.)
Yes. One way or the other I intend making it happen in the next few
months :-)
Andrew
prev parent reply other threads:[~2001-02-13 14:28 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
2001-02-13 14:28 ` Andrew Cagney [this message]
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=3A8983CD.8AC11A4B@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=hilfingr@gnat.com \
--cc=kevinb@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