Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: pedromfc@linux.ibm.com (Pedro Franco de Carvalho)
Cc: Alan.Hayward@arm.com (Alan Hayward),
	simark@simark.ca (Simon Marchi),
	       gdb-patches@sourceware.org (gdb-patches\@sourceware.org),
	       nd@arm.com (nd),
	anton@linux.ibm.com
Subject: Re: [PATCH 2/2] gdbserver: Add linux_get_hwcap
Date: Fri, 05 Apr 2019 16:39:00 -0000	[thread overview]
Message-ID: <20190405163946.2DB32D802DA@oc3748833570.ibm.com> (raw)
In-Reply-To: <875zrsctal.fsf@linux.vnet.ibm.com> from "Pedro Franco de Carvalho" at Apr 05, 2019 01:26:26 PM

Pedro Franco de Carvalho wrote: 

> Note that there is a difference in the interface between linux_get_auxv
> and linux_get_hwcap(2), the latter still return both the status and the
> entry value, but I didn't want to change all their users.

Actually, I think this is fine -- for hwcap, 0 is a natural default
value to use if the entry is not present.
 
> Also, contrary to the gdb client version (target_auxv_search
> gdb/auxv.c), this one doesn't differentiate between an error and the
> entry not being found.

That also seems reasonable.  If anybody requires more specific error
handling, that can always be added later.

> gdb/gdbserver/ChangeLog:
> 2019-04-DD  Pedro Franco de Carvalho  <pedromfc@linux.ibm.com>
> 
> 	* linux-low.c (linux_get_auxv): Remove static.  Return auxv entry
> 	value in argument pointer, return 1 if the entry is found and 0
> 	otherwise.  Move comment.
> 	(linux_get_hwcap, linux_get_hwcap2): Use modified linux_get_auxv.
> 	* linux-low.h (linux_get_auxv): Declare.
> 	* linux-ppc-low.c (is_elfv2_inferior): Use linux_get_auxv.

This is OK.

Thanks,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU/Linux compilers and toolchain
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2019-04-05 16:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25 12:05 [PATCH 1/2] " Alan Hayward
2019-03-25 12:05 ` [PATCH 2/2] gdbserver: " Alan Hayward
2019-03-25 15:41   ` Simon Marchi
2019-03-26 13:17     ` Alan Hayward
     [not found]       ` <353e83d9-efb3-c485-9ae6-6fc0a1f54553@simark.ca>
     [not found]         ` <57CEBD0C-44A5-48D1-8CEB-54584E1A1A21@arm.com>
     [not found]           ` <59A457A2-F464-4A05-A471-700F066114AD@arm.com>
2019-03-26 14:34             ` FW: " Alan Hayward
2019-03-28  9:50               ` Ulrich Weigand
2019-03-28 11:35                 ` Alan Hayward
2019-03-29 23:12                   ` Ulrich Weigand
2019-04-03 19:13                     ` Pedro Franco de Carvalho
2019-04-04 13:49                       ` Ulrich Weigand
2019-04-05 16:26                         ` Pedro Franco de Carvalho
2019-04-05 16:39                           ` Ulrich Weigand [this message]
2019-04-05 17:23                             ` Pedro Franco de Carvalho
2019-04-08  9:38                             ` Alan Hayward
2019-04-11 14:12                               ` Pedro Franco de Carvalho
2019-03-26 14:56             ` FW: " Simon Marchi
2019-04-02 22:00   ` Peter Bergner
2019-04-04 21:22     ` Pedro Franco de Carvalho
2019-03-25 15:18 ` [PATCH 1/2] " Simon Marchi
2019-03-25 16:51   ` Alan Hayward

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=20190405163946.2DB32D802DA@oc3748833570.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=Alan.Hayward@arm.com \
    --cc=anton@linux.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.com \
    --cc=pedromfc@linux.ibm.com \
    --cc=simark@simark.ca \
    /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