From: David Miller <davem@davemloft.net>
To: ast@fb.com
Cc: daniel@iogearbox.net, aconole@bytheb.org, netdev@vger.kernel.org,
xdp-newbies@vger.kernel.org
Subject: Re: [PATCH v3 binutils] Add BPF support to binutils...
Date: Mon, 01 May 2017 23:03:23 -0400 (EDT) [thread overview]
Message-ID: <20170501.230323.816591707269395321.davem@davemloft.net> (raw)
In-Reply-To: <b96ef138-9862-5091-9041-76516f852e48@fb.com>
From: Alexei Starovoitov <ast@fb.com>
Date: Mon, 1 May 2017 19:49:21 -0700
> On 4/30/17 11:21 AM, David Miller wrote:
>> built with:
>>
>> clang -O2 -target bpfel -g -c x.c -o x.o
>>
>> readelf can see it just fine:
>>
>> [davem@localhost binutils]$ ./readelf --debug-dump=loc ./xel.o
>> Contents of the .debug_loc section:
>>
>> Offset Begin End Expression
>> 00000000 0000000000000000 0000000000000010 (DW_OP_reg1 (r1))
>> 00000013 <End of list>
>> 00000023 0000000000000010 0000000000000020 (DW_OP_constu:
>> 590618314553; DW_OP_stack_value)
>> 0000003d 0000000000000020 0000000000000030 (DW_OP_reg1 (r1))
>> 00000050 <End of list>
>>
>> But with big-endian:
>>
>> [davem@localhost binutils]$ ./readelf --debug-dump=loc ./xeb.o
>> readelf: Warning: Invalid pointer size (0) in compunit header, using 4
>> instead
>> readelf: Warning: Bogus end-of-siblings marker detected at offset 27
>> in .debug_info section
>> readelf: Warning: Bogus end-of-siblings marker detected at offset 28
>> in .debug_info section
>> readelf: Warning: DIE at offset 0x29 refers to abbreviation number 48
>> which does not exist
>> readelf: Warning: Unable to load/parse the .debug_info section, so
>> cannot interpret the .debug_loc section.
>
> yeah. clang emitted dwarf for big-endian is broken.
> This dwarf stuff is too complicated for normal human beings.
> The tight packing making debugging it quite painful.
But doesn't the CLANG DWARF2 emission code look at the target
endianness?
next prev parent reply other threads:[~2017-05-02 3:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 20:33 [PATCH v3 binutils] Add BPF support to binutils David Miller
2017-04-30 0:48 ` Alexei Starovoitov
2017-04-30 2:11 ` David Miller
2017-04-30 2:13 ` David Miller
2017-04-30 2:24 ` Alexei Starovoitov
2017-04-30 2:24 ` David Miller
2017-04-30 2:37 ` David Miller
2017-04-30 6:44 ` Alexei Starovoitov
2017-04-30 15:28 ` David Miller
2017-04-30 15:40 ` David Miller
2017-04-30 18:21 ` David Miller
2017-05-02 2:49 ` Alexei Starovoitov
2017-05-02 3:03 ` David Miller [this message]
2017-05-02 3:14 ` Alexei Starovoitov
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=20170501.230323.816591707269395321.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aconole@bytheb.org \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=xdp-newbies@vger.kernel.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 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 NNTP newsgroup(s).