All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: James Le Cuirot <chewi@gentoo.org>
Cc: linux-media@vger.kernel.org, Sam James <sam@gentoo.org>
Subject: Re: [PATCH v2] meson: Allow BPF code to be built with GCC
Date: Tue, 12 Aug 2025 14:48:30 +0100	[thread overview]
Message-ID: <aJtGLpNHqsWTX6SY@gofer.mess.org> (raw)
In-Reply-To: <20250810142005.29811-2-chewi@gentoo.org>

On Sun, Aug 10, 2025 at 03:20:06PM +0100, James Le Cuirot wrote:
> GCC can also target BPF, but it does not understand the "-target bpf"
> arguments passed to Clang.
> 
> Detect it as either bpf-gcc, bpf-none-gcc, or bpf-unknown-none-gcc, the
> same as systemd does.
> 
> Determine the include paths with the compiler used by the rest of the
> build rather than Clang, which might not be installed or might not give
> the right answer, especially when cross-compiling.
> 
> Check whether Clang actually supports the BPF target so that
> auto-detection doesn't cause the build to fail when it doesn't.
> 
> Signed-off-by: James Le Cuirot <chewi@gentoo.org>

Applied. Thank you very much!

Sean

> ---
>  meson.build                                   | 25 ++++++++++++++++++-
>  .../keytable/bpf_protocols/cc_sys_includes.sh | 10 ++++++++
>  .../bpf_protocols/clang_sys_includes.sh       |  9 -------
>  utils/keytable/bpf_protocols/meson.build      | 12 ++++-----
>  utils/keytable/meson.build                    |  2 +-
>  5 files changed, 41 insertions(+), 17 deletions(-)
>  create mode 100755 utils/keytable/bpf_protocols/cc_sys_includes.sh
>  delete mode 100755 utils/keytable/bpf_protocols/clang_sys_includes.sh
> 
> This revision adds the -ftree-switch-conversion flag for GCC, which
> reportedly fixes the "invalid mem access" error. I couldn't figure out
> how to test without any hardware, so I wasn't able to reproduce the
> issue myself, but I trust that it works now.
> 
> diff --git a/meson.build b/meson.build
> index 88781e59..62d271b4 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -83,11 +83,34 @@ endif
>  v4l2_utils_incdir = include_directories(v4l2_utils_incdir_arr)
> 
>  prog_bash = find_program('bash')
> -prog_clang = find_program('clang', required : get_option('bpf'))
>  prog_doxygen = find_program('doxygen', required : get_option('doxygen-doc'))
>  prog_grep = find_program('grep')
>  prog_perl = find_program('perl')
> 
> +if get_option('bpf').allowed()
> +    bpf_args = []
> +    prog_bpf = find_program('bpf-gcc',
> +                            'bpf-none-gcc',
> +                            'bpf-unknown-none-gcc',
> +                            required : false)
> +
> +    if prog_bpf.found()
> +        bpf_args += ['-fno-tree-switch-conversion']
> +    else
> +        prog_bpf = find_program('clang', required : get_option('bpf'))
> +        if prog_bpf.found()
> +            target_bpf = run_command(prog_bpf, '-target', 'bpf', '--print-supported-cpus', check : get_option('bpf').enabled())
> +            if target_bpf.returncode() == 0
> +                bpf_args += ['-target', 'bpf']
> +            else
> +                prog_bpf = disabler()
> +            endif
> +        endif
> +    endif
> +else
> +    prog_bpf = disabler()
> +endif
> +
>  dep_alsa = dependency('alsa', required : false)
>  if dep_alsa.found()
>      conf.set('HAVE_ALSA', 1)
> diff --git a/utils/keytable/bpf_protocols/cc_sys_includes.sh b/utils/keytable/bpf_protocols/cc_sys_includes.sh
> new file mode 100755
> index 00000000..0a8fa277
> --- /dev/null
> +++ b/utils/keytable/bpf_protocols/cc_sys_includes.sh
> @@ -0,0 +1,10 @@
> +#!/bin/sh
> +# Get C compiler's default includes on this system, as the BPF toolchain
> +# generally doesn't see the Linux headers. This fixes "missing" files on some
> +# architectures/distros, such as asm/byteorder.h, asm/socket.h, asm/sockios.h,
> +# sys/cdefs.h etc.
> +#
> +# Use '-idirafter': Don't interfere with include mechanics except where the
> +# build would have failed anyways.
> +"$@" -v -E - </dev/null 2>&1 \
> +	| sed -n '/<...> search starts here:/,/End of search list./{ s| \(/.*\)|-idirafter \1|p }'
> diff --git a/utils/keytable/bpf_protocols/clang_sys_includes.sh b/utils/keytable/bpf_protocols/clang_sys_includes.sh
> deleted file mode 100755
> index 9dc4af12..00000000
> --- a/utils/keytable/bpf_protocols/clang_sys_includes.sh
> +++ /dev/null
> @@ -1,9 +0,0 @@
> -#!/bin/sh
> -# Get Clang's default includes on this system, as opposed to those seen by
> -# '-target bpf'. This fixes "missing" files on some architectures/distros,
> -# such as asm/byteorder.h, asm/socket.h, asm/sockios.h, sys/cdefs.h etc.
> -#
> -# Use '-idirafter': Don't interfere with include mechanics except where the
> -# build would have failed anyways.
> -$CLANG -v -E - </dev/null 2>&1 \
> -	| sed -n '/<...> search starts here:/,/End of search list./{ s| \(/.*\)|-idirafter \1|p }'
> diff --git a/utils/keytable/bpf_protocols/meson.build b/utils/keytable/bpf_protocols/meson.build
> index 1e4f0064..dbb926c4 100644
> --- a/utils/keytable/bpf_protocols/meson.build
> +++ b/utils/keytable/bpf_protocols/meson.build
> @@ -10,9 +10,9 @@ bpf_protocols_files = [
>      'xbox-dvd',
>  ]
> 
> -clang_sys_includes = run_command('clang_sys_includes.sh',
> -                                 check : true,
> -                                 env : ['CLANG=' + prog_clang.full_path()])
> +bpf_args += run_command('cc_sys_includes.sh',
> +                        cc.cmd_array(),
> +                        check : true).stdout().split()
> 
>  foreach file : bpf_protocols_files
>      output = file + '.o'
> @@ -21,9 +21,9 @@ foreach file : bpf_protocols_files
>                    output : output,
>                    input : input,
>                    command : [
> -                      prog_clang,
> -                      clang_sys_includes.stdout().split(),
> -                      '-D__linux__', '-fno-stack-protector', '-target', 'bpf',
> +                      prog_bpf,
> +                      bpf_args,
> +                      '-D__linux__', '-fno-stack-protector',
>                        '-O2', '-c', '@INPUT@', '-o', '@OUTPUT@',
>                    ],
>                    install : true,
> diff --git a/utils/keytable/meson.build b/utils/keytable/meson.build
> index e214e0b5..56e61a79 100644
> --- a/utils/keytable/meson.build
> +++ b/utils/keytable/meson.build
> @@ -22,7 +22,7 @@ ir_keytable_c_args = [
>      '-DIR_KEYTABLE_USER_DIR="@0@"'.format(ir_keytable_user_dir),
>  ]
> 
> -ir_bpf_enabled = prog_clang.found() and dep_libbpf.found() and dep_libelf.found()
> +ir_bpf_enabled = prog_bpf.found() and dep_libbpf.found() and dep_libelf.found()
> 
>  if ir_bpf_enabled
>      ir_keytable_sources += files(
> --
> 2.50.1

      reply	other threads:[~2025-08-12 13:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-03  8:17 [PATCH] meson: Allow BPF code to be built with GCC James Le Cuirot
2025-08-04  9:13 ` Sean Young
2025-08-04 20:22   ` Sam James
2025-08-04 20:34     ` James Le Cuirot
2025-08-05 11:32   ` Sean Young
2025-08-05 15:03     ` Sam James
2025-08-05 22:32       ` Sam James
2025-08-06 20:53         ` Sean Young
2025-08-06 21:09           ` Sam James
2025-08-08  1:19             ` Sam James
2025-08-08 12:42               ` Sean Young
2025-08-10 14:20 ` [PATCH v2] " James Le Cuirot
2025-08-12 13:48   ` Sean Young [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=aJtGLpNHqsWTX6SY@gofer.mess.org \
    --to=sean@mess.org \
    --cc=chewi@gentoo.org \
    --cc=linux-media@vger.kernel.org \
    --cc=sam@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.