From: Eli Zaretskii <eliz@gnu.org>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH V4 1/3] gdb: support for eBPF
Date: Fri, 10 Jul 2020 15:38:19 +0300 [thread overview]
Message-ID: <83blknpmtg.fsf@gnu.org> (raw)
In-Reply-To: <20200710122530.32541-2-jose.marchesi@oracle.com> (gdb-patches@sourceware.org)
> Date: Fri, 10 Jul 2020 14:25:28 +0200
> From: "Jose E. Marchesi via Gdb-patches" <gdb-patches@sourceware.org>
>
> This patch adds basic support for the eBPF target: tdep and build
> machinery. The accompanying simulator is introduced in subsequent
> patches.
>
> gdb/ChangeLog:
>
> 2020-07-10 Weimin Pan <weimin.pan@oracle.com>
> Jose E. Marchesi <jose.marchesi@oracle.com>
>
> * configure.tgt: Add entry for bpf-*-*.
> * Makefile.in (ALL_TARGET_OBS): Add bpf-tdep.o
> (HFILES_NO_SRCDIR): Add bpf-tdep.h.
> (ALLDEPFILES): Add bpf-tdep.c.
> * bpf-tdep.h: New file.
> * bpf-tdep.c: Likewise.
>
> gdb/doc/ChangeLog:
>
> 2020-07-10 Jose E. Marchesi <jose.marchesi@oracle.com>
>
> * gdb.texinfo (Contributors): Add information for the eBPF
> support.
> (BPF): New section.
Thanks, the documentation part is OK.
next prev parent reply other threads:[~2020-07-10 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 12:25 [PATCH V4 0/3] eBPF support Jose E. Marchesi
2020-07-10 12:25 ` [PATCH V4 1/3] gdb: support for eBPF Jose E. Marchesi
2020-07-10 12:38 ` Eli Zaretskii [this message]
2020-07-10 13:51 ` Simon Marchi
2020-07-10 14:29 ` Jose E. Marchesi
2020-07-10 14:49 ` Simon Marchi
2020-07-10 12:25 ` [PATCH V4 2/3] sim: eBPF simulator Jose E. Marchesi
2020-07-12 8:25 ` Andrew Burgess
2020-07-12 10:06 ` Jose E. Marchesi
2020-07-10 12:25 ` [PATCH V4 3/3] sim: generated files for the " Jose E. Marchesi
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=83blknpmtg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.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