All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yaniv Agman <yanivagman@gmail.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: libbpf error: unknown register name 'r0' in asm
Date: Fri, 9 Oct 2020 21:12:28 +0300	[thread overview]
Message-ID: <CAMy7=ZURAvNoAtdUK5-zQVDMvbnwqnEJOTJ27WeZNMFYoLSnfg@mail.gmail.com> (raw)
In-Reply-To: <CAEf4BzYTja99-1LHdMK69qY3XrqgtyKVheV3YH7e89JY0C4E1A@mail.gmail.com>

‫בתאריך יום ו׳, 9 באוק׳ 2020 ב-21:03 מאת ‪Andrii Nakryiko‬‏
<‪andrii.nakryiko@gmail.com‬‏>:‬
>
> On Fri, Oct 9, 2020 at 9:06 AM Yaniv Agman <yanivagman@gmail.com> wrote:
> >
> > Pulling the latest changes of libbpf and compiling my application with it,
> > I see the following error:
> >
> > ../libbpf/src//root/usr/include/bpf/bpf_helpers.h:99:10: error:
> > unknown register name 'r0' in asm
> >                      : "r0", "r1", "r2", "r3", "r4", "r5");
>
> are you including bpf_helpers.h from user-space code? You are using
> recent enough Clang to not run into this problem for -target bpf, so
> this seems like you are including bpf_helpers.h in the context where
> it's not supposed to be included.
>

This happens when I compile the kernel bpf code, not for user-space code

>
> >
> > The commit which introduced this change is:
> > 80c7838600d39891f274e2f7508b95a75e4227c1
> >
> > I'm not sure if I'm doing something wrong (missing include?), or this
> > is a genuine error
> >
> > Yaniv

      reply	other threads:[~2020-10-09 18:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 16:05 libbpf error: unknown register name 'r0' in asm Yaniv Agman
2020-10-09 16:27 ` Daniel Borkmann
2020-10-09 16:56   ` Yaniv Agman
2020-10-09 17:39     ` Daniel Borkmann
2020-10-09 18:09       ` Yaniv Agman
2020-10-09 18:21         ` Daniel Borkmann
2020-10-09 18:33           ` Yaniv Agman
2020-10-09 18:39             ` Andrii Nakryiko
2020-10-09 19:32               ` Yaniv Agman
2020-10-09 19:53                 ` Andrii Nakryiko
2020-10-09 20:24                   ` Yaniv Agman
2020-10-12 20:03                     ` Andrii Nakryiko
2020-10-12 21:48                       ` Yaniv Agman
2020-10-12 22:16                         ` Andrii Nakryiko
2020-10-09 18:35           ` Andrii Nakryiko
2020-10-09 18:41             ` Daniel Borkmann
2020-10-09 18:59               ` Andrii Nakryiko
2020-10-09 19:08                 ` Yonghong Song
2020-10-09 19:33                   ` Yaniv Agman
2020-10-09 19:58                     ` Daniel Borkmann
2020-10-21  9:43                       ` Yaniv Agman
2020-10-21 17:18                         ` Daniel Borkmann
2020-10-21 19:33                           ` Yaniv Agman
2020-10-09 17:41   ` Yonghong Song
2020-10-09 18:03 ` Andrii Nakryiko
2020-10-09 18:12   ` Yaniv Agman [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='CAMy7=ZURAvNoAtdUK5-zQVDMvbnwqnEJOTJ27WeZNMFYoLSnfg@mail.gmail.com' \
    --to=yanivagman@gmail.com \
    --cc=andrii.nakryiko@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    /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.