Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] ptid_{lwp,tid}_p: Remove unnecessary checks
Date: Wed, 05 Apr 2017 15:15:00 -0000	[thread overview]
Message-ID: <15fd0842-2c1d-3567-f707-3de79fa84e67@redhat.com> (raw)
In-Reply-To: <20170404183235.10589-1-simon.marchi@ericsson.com>

On 04/04/2017 07:32 PM, Simon Marchi wrote:
> The calls to ptid_equal in ptid_lwp_p and ptid_tid_p that compare the
> argument to minus_one_ptid and null_ptid are not necessary.  The calls
> in question are:
> 
>    if (ptid_equal (minus_one_ptid, ptid)
>        || ptid_equal (null_ptid, ptid))
>      return 0;
> 
> minus_one_ptid is { .pid = -1, .lwp = 0, .tid = 0 }
> null_ptid is { .pid = 0, .lwp = 0, .tid = 0 }
> 
> If the ptid argument is either of them, the statements
> 
>   return (ptid_get_lwp (ptid) != 0);
> 
> and
> 
>   return (ptid_get_tid (ptid) != 0);
> 
> will yield the same result (0/false).
> 
> gdb/ChangeLog:
> 
> 	* common/ptid.c (ptid_lwp_p, ptid_tid_p): Remove comparison with
> 	minus_one_ptid and null_ptid.

Indeed.  LGTM.

Thanks,
Pedro Alves


  parent reply	other threads:[~2017-04-05 15:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 18:32 Simon Marchi
2017-04-04 18:33 ` [PATCH 2/2] Class-ify ptid_t Simon Marchi
2017-04-05 15:47   ` Pedro Alves
2017-04-05 19:44     ` Simon Marchi
2017-04-05 21:31       ` Pedro Alves
2017-04-06  2:15         ` Simon Marchi
2017-04-06 10:49           ` Pedro Alves
2017-04-06 11:12             ` Pedro Alves
2017-04-06 14:32               ` Simon Marchi
2017-04-06 14:38                 ` Pedro Alves
2017-04-06  3:09         ` Simon Marchi
2017-04-06 11:06           ` Pedro Alves
2017-04-05 15:15 ` Pedro Alves [this message]
2017-04-05 19:21   ` [PATCH 1/2] ptid_{lwp,tid}_p: Remove unnecessary checks Simon Marchi

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=15fd0842-2c1d-3567-f707-3de79fa84e67@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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