From: Michael Chastain <mec.gnu@mindspring.com>
To: msnyder@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite/threads] fix gcc signed/unsigned warning
Date: Fri, 27 Aug 2004 11:23:00 -0000 [thread overview]
Message-ID: <412F199A.nailK3I21D250@mindspring.com> (raw)
In-Reply-To: <412E9F3A.4010200@redhat.com>
Michael Snyder <msnyder@redhat.com> wrote:
> But if you want to just do this, it's OK with me.
Yay, committed.
> Well, it really looks to me as if either args should be
> signed, or myp should be unsigned. The test will work
> either way, although signed would "feel" safer.
I fooled around with this. I couldn't find something that was type-safe
and felt exactly like the old test. So I decided "one thing at a time"
-- first make it compile like it did with old compilers, then later, fix
the signed/unsigned muddle.
I've filed a PR for the signed/unsigned part.
===
2004-08-26 Michael Chastain <mec.gnu@mindspring.com>
Fix PR testsuite/1735.
* gdb.threads/schedlock.c (thread_function): Add a cast
to suppress a gcc warning.
* gdb.threads/thread-specific.c (thread_function): Likewise.
prev parent reply other threads:[~2004-08-27 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 17:03 Michael Chastain
2004-08-27 2:41 ` Michael Snyder
2004-08-27 11:23 ` Michael Chastain [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=412F199A.nailK3I21D250@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@redhat.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