Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: nicolas.blanc@intel.com
Cc: gdb-patches@sourceware.org, dje@google.com, nicolas.blanc@intel.com
Subject: Re: [PATCH v12 4/5] Function is_elf_target.
Date: Wed, 17 Jul 2013 18:43:00 -0000	[thread overview]
Message-ID: <201307171843.r6HIhWEQ006115@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <1374078455-906-5-git-send-email-nicolas.blanc@intel.com>	(message from Nicolas Blanc on Wed, 17 Jul 2013 18:27:34 +0200)

> From: Nicolas Blanc <nicolas.blanc@intel.com>
> Date: Wed, 17 Jul 2013 18:27:34 +0200
> 
> 2013-17-07  Nicolas Blanc  <nicolas.blanc@intel.com>
> 
> gdb/testsuite
> 	* lib/gdb.exp (is_elf_target): New function.
> 
> Signed-off-by: Nicolas Blanc <nicolas.blanc@intel.com>

That's a very incomplete list.

I think a better solution is needed.  Instead of whitelisting targets
for what is basically the default, blacklisting targets that aren't
ELF would be a better approach.

> ---
>  gdb/testsuite/lib/gdb.exp |   15 +++++++++++++++
>  1 files changed, 15 insertions(+), 0 deletions(-)
> 
> diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
> index 376aacc..8c5cdb5 100644
> --- a/gdb/testsuite/lib/gdb.exp
> +++ b/gdb/testsuite/lib/gdb.exp
> @@ -1782,6 +1782,21 @@ proc supports_reverse {} {
>      return 0
>  }
>  
> +# Return 1 if target supports ELF.
> +proc is_elf_target {} {
> +
> +    if { [istarget "*-*-linux*"]
> +	 || [istarget "*-*-gnu*"]
> +	 || [istarget "*-*-elf*"]
> +	 || [istarget "arm*-*-eabi*"]
> +	 || [istarget "arm*-*-symbianelf*"]
> +	 || [istarget "powerpc-*-eabi*"] } {
> +	return 1
> +    }
> +
> +    return 0
> +}
> +
>  # Return 1 if target is ILP32.
>  # This cannot be decided simply from looking at the target string,
>  # as it might depend on externally passed compiler options like -m64.
> -- 
> 1.7.6.5
> 
> 


  reply	other threads:[~2013-07-17 18:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 16:28 [PATCH v12 0/5] remove-symbol-file & add-symbol-file Nicolas Blanc
2013-07-17 16:27 ` [PATCH v12 1/5] New remove-symbol-file command Nicolas Blanc
2013-07-17 16:27 ` [PATCH v12 2/5] Documentation for the " Nicolas Blanc
2013-07-17 17:02   ` Eli Zaretskii
2013-07-17 16:27 ` [PATCH v12 4/5] Function is_elf_target Nicolas Blanc
2013-07-17 18:43   ` Mark Kettenis [this message]
2013-07-17 19:47     ` Doug Evans
2013-07-17 16:28 ` [PATCH v12 3/5] 'add-symbol-file' should update the current target sections Nicolas Blanc
2013-07-26 19:10   ` Luis Machado
2013-07-17 16:28 ` [PATCH v12 5/5] Test adding and removing a symbol file at runtime Nicolas Blanc
2013-07-17 18:53   ` Mark Kettenis
2013-07-18 12:52     ` Blanc, Nicolas
2013-07-18 13:28       ` Mark Kettenis
2013-07-18 16:05         ` Blanc, Nicolas

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=201307171843.r6HIhWEQ006115@glazunov.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nicolas.blanc@intel.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