public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
	"Jose E. Marchesi" <jemarch@gnu.org>
Cc: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: [PATCH V6 05/11] bpf: new GCC port
Date: Tue, 03 Sep 2019 18:46:00 -0000	[thread overview]
Message-ID: <6055ae30-5c7c-f990-0605-9ee09c492fd0@redhat.com> (raw)
In-Reply-To: <87h85zf0td.fsf@oracle.com>

On 8/30/19 3:40 AM, Jose E. Marchesi wrote:
> 
>     > This patch adds a port for the Linux kernel eBPF architecture to GCC.
>     >
>     > ChangeLog:
>     >
>     >   * configure.ac: Support for bpf-*-* targets.
>     >   * configure: Regenerate.
>     >
>     > contrib/ChangeLog:
>     >
>     >   * config-list.mk (LIST): Disable go in bpf-*-* targets.
>     >
>     > gcc/ChangeLog:
>     >
>     >   * config.gcc: Support for bpf-*-* targets.
>     >   * common/config/bpf/bpf-common.c: New file.
>     >   * config/bpf/t-bpf: Likewise.
>     >   * config/bpf/predicates.md: Likewise.
>     >   * config/bpf/constraints.md: Likewise.
>     >   * config/bpf/bpf.opt: Likewise.
>     >   * config/bpf/bpf.md: Likewise.
>     >   * config/bpf/bpf.h: Likewise.
>     >   * config/bpf/bpf.c: Likewise.
>     >   * config/bpf/bpf-protos.h: Likewise.
>     >   * config/bpf/bpf-opts.h: Likewise.
>     >   * config/bpf/bpf-helpers.h: Likewise.
>     >   * config/bpf/bpf-helpers.def: Likewise.
>     
>     Looks good to me, thanks.
> 
> Thanks to you for the throughful, super useful review.
> 
>     Jeff also had detailed comments, so please wait for an ack from him
>     too.
>     
> Sure.
I think the bits are in good enough shape they can go in now.

jeff

  reply	other threads:[~2019-09-03 18:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 15:32 [PATCH V6 00/11] eBPF support for GCC Jose E. Marchesi
2019-08-29 15:14 ` [PATCH V6 03/11] testsuite: annotate c-torture/compile tests with dg-require-stack-size Jose E. Marchesi
2019-09-09  9:52   ` Jose E. Marchesi
2019-09-11 18:42   ` Mike Stump
2019-09-11 20:49     ` Jose E. Marchesi
2019-08-29 15:14 ` [PATCH V6 04/11] testsuite: new require effective target indirect_calls Jose E. Marchesi
2019-09-09  9:56   ` Jose E. Marchesi
2019-09-11 18:55   ` Mike Stump
2019-09-11 20:47     ` Jose E. Marchesi
2019-09-12  0:43       ` Mike Stump
2019-08-29 15:16 ` [PATCH V6 08/11] bpf: make target-supports.exp aware of eBPF Jose E. Marchesi
2019-09-11 18:58   ` Mike Stump
2019-09-12  0:35     ` Mike Stump
2019-08-29 15:16 ` [PATCH V6 07/11] bpf: gcc.target eBPF testsuite Jose E. Marchesi
2019-08-29 15:18 ` [PATCH V6 10/11] bpf: manual updates for eBPF Jose E. Marchesi
2019-08-29 15:18 ` [PATCH V6 11/11] bpf: add myself as the maintainer for the eBPF port Jose E. Marchesi
2019-09-08 11:36   ` Gerald Pfeifer
2019-09-08 16:39     ` Jose E. Marchesi
2019-10-07 18:52     ` Thomas Schwinge
2019-08-29 15:20 ` [PATCH V6 01/11] Update config.sub and config.guess Jose E. Marchesi
2019-09-09  9:17   ` Jose E. Marchesi
2019-08-29 15:21 ` [PATCH V6 06/11] bpf: new libgcc port Jose E. Marchesi
2019-08-29 15:21 ` [PATCH V6 09/11] bpf: adjust GCC testsuite to eBPF limitations Jose E. Marchesi
2019-09-11 19:04   ` Mike Stump
2019-08-29 15:34 ` [PATCH V6 02/11] opt-functions.awk: fix comparison of limit, begin and end Jose E. Marchesi
2019-09-09  9:47   ` Jose E. Marchesi
2019-08-29 15:36 ` [PATCH V6 05/11] bpf: new GCC port Jose E. Marchesi
2019-08-30  8:38   ` Richard Sandiford
2019-08-30 10:11     ` Jose E. Marchesi
2019-09-03 18:46       ` Jeff Law [this message]
2019-09-05 22:50         ` Jose E. Marchesi
2019-09-11 19:09           ` Mike Stump
2019-09-09 10:23         ` Jose E. Marchesi
2019-10-20 19:51           ` Gerald Pfeifer
2019-10-24  8:45             ` 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=6055ae30-5c7c-f990-0605-9ee09c492fd0@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jemarch@gnu.org \
    --cc=jose.marchesi@oracle.com \
    --cc=richard.sandiford@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).