All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: Sam James <sam@gentoo.org>
Cc: James Le Cuirot <chewi@gentoo.org>, linux-media@vger.kernel.org
Subject: Re: [PATCH] meson: Allow BPF code to be built with GCC
Date: Fri, 8 Aug 2025 13:42:26 +0100	[thread overview]
Message-ID: <aJXwsll4gi8W7cTw@gofer.mess.org> (raw)
In-Reply-To: <87ikiyzk2i.fsf@gentoo.org>

On Fri, Aug 08, 2025 at 02:19:33AM +0100, Sam James wrote:
> Sam James <sam@gentoo.org> writes:
> > Sean Young <sean@mess.org> writes:
> >> The problem is that gcc compiles this down to a lookup table which is then
> >> stored in the .rodata section.
> >>
> >> https://git.linuxtv.org/v4l-utils.git/tree/utils/keytable/bpf_protocols/imon_rsc.c#n97
> >>
> >> Then ir-keytable fails to load and relocate the rodata section. Note the 
> >> error:
> >>
> >> symbol  has unknown section 6
> >>
> >> section 6 is the rodata section.
> >>
> >> ir-keytable simply has no handling for .rodata right now. I am not sure how
> >> bpf handles .rodata (if at all), needs more investigation.
> >
> 
> With -fno-tree-switch-conversion, the program loads for me.

Yes, that works. Let's use that in meson.build.

Thanks,

Sean

  reply	other threads:[~2025-08-08 12:42 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 [this message]
2025-08-10 14:20 ` [PATCH v2] " James Le Cuirot
2025-08-12 13:48   ` Sean Young

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=aJXwsll4gi8W7cTw@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.