From: Jiri Olsa <jolsa@redhat.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Veronika Kabatova <vkabatov@redhat.com>,
Andrii Nakryiko <andriin@fb.com>,
Alexei Starovoitov <ast@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
bpf <bpf@vger.kernel.org>, "Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: Build failures: unresolved symbol vfs_getattr
Date: Fri, 16 Oct 2020 23:38:35 +0200 [thread overview]
Message-ID: <20201016213835.GJ1461394@krava> (raw)
In-Reply-To: <20200916090624.GD2301783@krava>
On Wed, Sep 16, 2020 at 11:06:27AM +0200, Jiri Olsa wrote:
> On Tue, Sep 15, 2020 at 02:17:46PM +0200, Jiri Olsa wrote:
>
> SNIP
>
> > <2><140d7aa>: Abbrev Number: 3 (DW_TAG_formal_parameter)
> > <140d7ab> DW_AT_type : <0x140cfb6>
> > <2><140d7af>: Abbrev Number: 3 (DW_TAG_formal_parameter)
> > <140d7b0> DW_AT_type : <0x1406176>
> > <2><140d7b4>: Abbrev Number: 3 (DW_TAG_formal_parameter)
> > <140d7b5> DW_AT_type : <0x14060c9>
> > <2><140d7b9>: Abbrev Number: 0
> >
> > the latter is just declaration.. but it's missing the
> > <365d69d> DW_AT_declaration : 1
> >
> > so it goes through pahole's function processing:
> >
> > cu__encode_btf:
> > ...
> > cu__for_each_function(cu, core_id, fn) {
> > int btf_fnproto_id, btf_fn_id;
> >
> > if (fn->declaration || !fn->external)
> > continue;
> > ...
> >
> >
> > CC-ing Frank.. any idea why is the DW_AT_declaration : 1 missing?
>
> looks like gcc issue:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97060
>
> let's see ;-)
so this gcc bug did not disappear and the fix might be delayed,
as I was told it's real complex and difficult to fix
and it's no longer just rawhide issue, because I just started to
see it in Fedora 32 after updating to gcc (GCC) 10.2.1 20201005
(Red Hat 10.2.1-5)
I'm checking on pahole's workaround, but so far I can't see dwarf
based solution for that.. any thoughts/ideas? ;-)
thanks,
jirka
next prev parent reply other threads:[~2020-10-16 21:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1723352278.11013122.1600093319730.JavaMail.zimbra@redhat.com>
2020-09-14 14:48 ` Build failures: unresolved symbol vfs_getattr Veronika Kabatova
2020-09-14 18:25 ` Jiri Olsa
2020-09-14 22:26 ` Andrii Nakryiko
2020-09-15 7:30 ` Jiri Olsa
2020-09-15 12:17 ` Jiri Olsa
2020-09-16 9:06 ` Jiri Olsa
2020-10-16 21:38 ` Jiri Olsa [this message]
2020-10-21 19:42 ` Jiri Olsa
2020-10-22 20:00 ` Andrii Nakryiko
2020-10-23 5:36 ` Jiri Olsa
2020-10-23 6:58 ` Jiri Olsa
2020-10-23 18:22 ` Andrii Nakryiko
2020-10-23 20:17 ` Jiri Olsa
2020-10-23 20:32 ` Andrii Nakryiko
2020-10-23 20:45 ` Jiri Olsa
2020-10-23 22:02 ` Andrii Nakryiko
2020-10-26 10:14 ` Jiri Olsa
2020-10-26 22:06 ` Andrii Nakryiko
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=20201016213835.GJ1461394@krava \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=fche@redhat.com \
--cc=vkabatov@redhat.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 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.