Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: John Baldwin <jhb@FreeBSD.org>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH v3 3/3] Add native target for FreeBSD/mips.
Date: Tue, 03 Jan 2017 19:15:00 -0000	[thread overview]
Message-ID: <838tqsez0i.fsf@gnu.org> (raw)
In-Reply-To: <20170103184341.58346-4-jhb@FreeBSD.org> (message from John	Baldwin on Tue, 3 Jan 2017 10:43:41 -0800)

> From: John Baldwin <jhb@FreeBSD.org>
> Date: Tue,  3 Jan 2017 10:43:41 -0800
> 
> This supports the o32 and n64 ABIs.
> 
> gdb/ChangeLog:
> 
> 	* Makefile.in (ALLDEPFILES): Add mips-fbsd-nat.c.
> 	* NEWS: Mention new FreeBSD/mips native configuration.
> 	* config/mips/fbsd.mh: New file.
> 	* configure.host: Add mips*-*-freebsd*.
> 	* mips-fbsd-nat.c: New file.
> ---
>  gdb/ChangeLog           |   8 +++
>  gdb/Makefile.in         |   1 +
>  gdb/NEWS                |   5 ++
>  gdb/config/mips/fbsd.mh |   3 ++
>  gdb/configure.host      |   1 +
>  gdb/mips-fbsd-nat.c     | 136 ++++++++++++++++++++++++++++++++++++++++++++++++
>  6 files changed, 154 insertions(+)
>  create mode 100644 gdb/config/mips/fbsd.mh
>  create mode 100644 gdb/mips-fbsd-nat.c
> 
> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
> index dea01e7025..a8caa9bf9d 100644
> --- a/gdb/ChangeLog
> +++ b/gdb/ChangeLog
> @@ -1,5 +1,13 @@
>  2017-01-03  John Baldwin  <jhb@FreeBSD.org>
>  
> +	* Makefile.in (ALLDEPFILES): Add mips-fbsd-nat.c.
> +	* NEWS: Mention new FreeBSD/mips native configuration.
> +	* config/mips/fbsd.mh: New file.
> +	* configure.host: Add mips*-*-freebsd*.
> +	* mips-fbsd-nat.c: New file.
> +
> +2017-01-03  John Baldwin  <jhb@FreeBSD.org>
> +
>  	* Makefile.in (ALL_TARGET_OBS): Add mips-fbsd-tdep.o.
>  	(ALLDEPFILES): Add mips-fbsd-tdep.c.
>  	* NEWS: Mention new FreeBSD/mips target.
> diff --git a/gdb/Makefile.in b/gdb/Makefile.in
> index f20b97347a..f5f15c23c1 100644
> --- a/gdb/Makefile.in
> +++ b/gdb/Makefile.in
> @@ -2541,6 +2541,7 @@ ALLDEPFILES = \
>  	microblaze-linux-tdep.c \
>  	microblaze-tdep.c \
>  	mingw-hdep.c \
> +	mips-fbsd-nat.c \
>  	mips-fbsd-tdep.c \
>  	mips-linux-nat.c \
>  	mips-linux-tdep.c \
> diff --git a/gdb/NEWS b/gdb/NEWS
> index f7fe9aeb76..b9768159cd 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -47,6 +47,11 @@
>       end
>     end
>  
> +* New native configurations
> +
> +FreeBSD/mips			mips*-*-freebsd
> +
> +
>  * New targets
>  
>  Synopsys ARC			arc*-*-elf32

OK for the NEWS part.

Thanks.


      reply	other threads:[~2017-01-03 19:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 18:45 [PATCH v3 0/3] Add FreeBSD/mips targets to GDB John Baldwin
2017-01-03 18:45 ` [PATCH v3 1/3] Use bfd_mach_mips4000 as the default machine type for 64-bit MIPS ABIs John Baldwin
2017-01-04  2:09   ` Maciej W. Rozycki
2017-01-04  3:09     ` John Baldwin
2017-01-03 18:45 ` [PATCH v3 2/3] Add FreeBSD/mips architecture John Baldwin
2017-01-03 19:05   ` Luis Machado
2017-01-03 20:12     ` John Baldwin
2017-01-03 19:16   ` Eli Zaretskii
2017-01-04 21:23   ` Luis Machado
2017-01-04 22:10     ` John Baldwin
2017-01-05  0:52       ` Luis Machado
2017-01-03 18:45 ` [PATCH v3 3/3] Add native target for FreeBSD/mips John Baldwin
2017-01-03 19:15   ` Eli Zaretskii [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=838tqsez0i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.org \
    /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