From: Luis Machado <luis.machado@arm.com>
To: Alan Modra <amodra@gmail.com>, Nick Clifton <nickc@redhat.com>,
Kavitha.Natarajan@amd.com
Cc: binutils@sourceware.org
Subject: Re: [PATCH] Binutils support for DWARF-5 DW_OP_addrx
Date: Thu, 26 May 2022 08:19:57 +0100 [thread overview]
Message-ID: <2b884fc9-ab24-4303-027e-ce1d9c552add@arm.com> (raw)
In-Reply-To: <Yo6+8DMmlvZeTqFM@squeak.grove.modra.org>
On 5/26/22 00:42, Alan Modra via Binutils wrote:
> On Wed, May 25, 2022 at 04:13:31PM +0100, Nick Clifton wrote:
>> Hi Kavitha,
>>
>> Thanks for the revised patch. I have gone ahead and
>> applied it to the sources.
>
> And now with the missing testsuite files committed, which needed
> editing to fix whitespace. (Presumably Kavitha's email client
> "helpfully" expanded tabs.)
>
> I also fixed the endian issue in dw5-op.W that caused the following:
> aarch64_be-linux-gnu_ilp32 +FAIL: objdump -Wi for DW_OP_*
> aarch64_be-linux-gnu_ilp32 +FAIL: readelf -wi dw5-op
> armeb-linuxeabi +FAIL: objdump -Wi for DW_OP_*
> armeb-linuxeabi +FAIL: readelf -wi dw5-op
> d10v-elf +FAIL: objdump -Wi for DW_OP_*
> d10v-elf +FAIL: readelf -wi dw5-op
> d30v-elf +FAIL: objdump -Wi for DW_OP_*
> d30v-elf +FAIL: readelf -wi dw5-op
> dlx-elf +FAIL: objdump -Wi for DW_OP_*
> dlx-elf +FAIL: readelf -wi dw5-op
> fr30-elf +FAIL: objdump -Wi for DW_OP_*
> fr30-elf +FAIL: readelf -wi dw5-op
> frv-elf +FAIL: objdump -Wi for DW_OP_*
> frv-elf +FAIL: readelf -wi dw5-op
> frv-linux +FAIL: objdump -Wi for DW_OP_*
> frv-linux +FAIL: readelf -wi dw5-op
> h8300-elf +FAIL: objdump -Wi for DW_OP_*
> h8300-elf +FAIL: readelf -wi dw5-op
> h8300-linux +FAIL: objdump -Wi for DW_OP_*
> h8300-linux +FAIL: readelf -wi dw5-op
> hppa64-hp-hpux11.23 +FAIL: objdump -Wi for DW_OP_*
> hppa64-hp-hpux11.23 +FAIL: readelf -wi dw5-op
> hppa64-linux +FAIL: objdump -Wi for DW_OP_*
> hppa64-linux +FAIL: readelf -wi dw5-op
> hppa-linux +FAIL: objdump -Wi for DW_OP_*
> hppa-linux +FAIL: readelf -wi dw5-op
> ia64-hpux +FAIL: objdump -Wi for DW_OP_*
> ia64-hpux +FAIL: readelf -wi dw5-op
> ip2k-elf +FAIL: objdump -Wi for DW_OP_*
> ip2k-elf +FAIL: readelf -wi dw5-op
> iq2000-elf +FAIL: objdump -Wi for DW_OP_*
> iq2000-elf +FAIL: readelf -wi dw5-op
> lm32-elf +FAIL: objdump -Wi for DW_OP_*
> lm32-elf +FAIL: readelf -wi dw5-op
> lm32-linux +FAIL: objdump -Wi for DW_OP_*
> lm32-linux +FAIL: readelf -wi dw5-op
> m32r-elf +FAIL: objdump -Wi for DW_OP_*
> m32r-elf +FAIL: readelf -wi dw5-op
> m32r-linux +FAIL: objdump -Wi for DW_OP_*
> m32r-linux +FAIL: readelf -wi dw5-op
> m68hc11-elf +FAIL: objdump -Wi for DW_OP_*
> m68hc11-elf +FAIL: readelf -wi dw5-op
> m68hc12-elf +FAIL: objdump -Wi for DW_OP_*
> m68hc12-elf +FAIL: readelf -wi dw5-op
> m68k-elf +FAIL: objdump -Wi for DW_OP_*
> m68k-elf +FAIL: readelf -wi dw5-op
> m68k-linux +FAIL: objdump -Wi for DW_OP_*
> m68k-linux +FAIL: readelf -wi dw5-op
> microblaze-elf +FAIL: objdump -Wi for DW_OP_*
> microblaze-elf +FAIL: readelf -wi dw5-op
> microblaze-linux +FAIL: objdump -Wi for DW_OP_*
> microblaze-linux +FAIL: readelf -wi dw5-op
> mips64-linux +FAIL: objdump -Wi for DW_OP_*
> mips64-linux +FAIL: readelf -wi dw5-op
> mips64-openbsd +FAIL: objdump -Wi for DW_OP_*
> mips64-openbsd +FAIL: readelf -wi dw5-op
> mips-linux +FAIL: objdump -Wi for DW_OP_*
> mips-linux +FAIL: readelf -wi dw5-op
> mips-sgi-irix6 +FAIL: objdump -Wi for DW_OP_*
> mips-sgi-irix6 +FAIL: readelf -wi dw5-op
> mipstx39-elf +FAIL: objdump -Wi for DW_OP_*
> mipstx39-elf +FAIL: readelf -wi dw5-op
> moxie-elf +FAIL: objdump -Wi for DW_OP_*
> moxie-elf +FAIL: readelf -wi dw5-op
> mt-elf +FAIL: objdump -Wi for DW_OP_*
> mt-elf +FAIL: readelf -wi dw5-op
> nds32be-elf +FAIL: objdump -Wi for DW_OP_*
> nds32be-elf +FAIL: readelf -wi dw5-op
> or1k-elf +FAIL: objdump -Wi for DW_OP_*
> or1k-elf +FAIL: readelf -wi dw5-op
> or1k-linux +FAIL: objdump -Wi for DW_OP_*
> or1k-linux +FAIL: readelf -wi dw5-op
> pj-elf +FAIL: objdump -Wi for DW_OP_*
> pj-elf +FAIL: readelf -wi dw5-op
> powerpc64-freebsd +FAIL: objdump -Wi for DW_OP_*
> powerpc64-freebsd +FAIL: readelf -wi dw5-op
> powerpc64-linux +FAIL: objdump -Wi for DW_OP_*
> powerpc64-linux +FAIL: readelf -wi dw5-op
> powerpc-eabisim +FAIL: objdump -Wi for DW_OP_*
> powerpc-eabisim +FAIL: readelf -wi dw5-op
> powerpc-eabivle +FAIL: objdump -Wi for DW_OP_*
> powerpc-eabivle +FAIL: readelf -wi dw5-op
> powerpc-freebsd +FAIL: objdump -Wi for DW_OP_*
> powerpc-freebsd +FAIL: readelf -wi dw5-op
> powerpc-linux +FAIL: objdump -Wi for DW_OP_*
> powerpc-linux +FAIL: readelf -wi dw5-op
> powerpc-nto +FAIL: objdump -Wi for DW_OP_*
> powerpc-nto +FAIL: readelf -wi dw5-op
> s12z-elf +FAIL: objdump -Wi for DW_OP_*
> s12z-elf +FAIL: readelf -wi dw5-op
> s390-linux +FAIL: objdump -Wi for DW_OP_*
> s390-linux +FAIL: readelf -wi dw5-op
> s390x-linux +FAIL: objdump -Wi for DW_OP_*
> s390x-linux +FAIL: readelf -wi dw5-op
> score-elf +FAIL: objdump -Wi for DW_OP_*
> score-elf +FAIL: readelf -wi dw5-op
> sh-nto +FAIL: objdump -Wi for DW_OP_*
> sh-nto +FAIL: readelf -wi dw5-op
> sh-rtems +FAIL: objdump -Wi for DW_OP_*
> sh-rtems +FAIL: readelf -wi dw5-op
> sparc64-linux +FAIL: objdump -Wi for DW_OP_*
> sparc64-linux +FAIL: readelf -wi dw5-op
> sparc-elf +FAIL: objdump -Wi for DW_OP_*
> sparc-elf +FAIL: readelf -wi dw5-op
> sparc-linux +FAIL: objdump -Wi for DW_OP_*
> sparc-linux +FAIL: readelf -wi dw5-op
> sparc-sun-solaris2 +FAIL: objdump -Wi for DW_OP_*
> sparc-sun-solaris2 +FAIL: readelf -wi dw5-op
> spu-elf +FAIL: objdump -Wi for DW_OP_*
> spu-elf +FAIL: readelf -wi dw5-op
> visium-elf +FAIL: objdump -Wi for DW_OP_*
> visium-elf +FAIL: readelf -wi dw5-op
> xgate-elf +FAIL: objdump -Wi for DW_OP_*
> xgate-elf +FAIL: readelf -wi dw5-op
> xtensa-elf +FAIL: objdump -Wi for DW_OP_*
> xtensa-elf +FAIL: readelf -wi dw5-op
>
I suppose that's the hiccup the buildbot caught?
next prev parent reply other threads:[~2022-05-26 7:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 10:14 Natarajan, Kavitha
2022-04-29 14:21 ` Nick Clifton
2022-05-20 10:38 ` Natarajan, Kavitha
2022-05-25 15:13 ` Nick Clifton
2022-05-25 23:42 ` Alan Modra
2022-05-26 4:35 ` Natarajan, Kavitha
2022-05-26 7:19 ` Luis Machado [this message]
2022-05-26 8:04 ` Alan Modra
2022-05-26 8:06 ` Luis Machado
-- strict thread matches above, loose matches on Subject: below --
2022-04-27 10:33 Natarajan, Kavitha
2022-04-28 9:54 ` Nick Clifton
2022-04-28 10:19 ` Natarajan, Kavitha
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=2b884fc9-ab24-4303-027e-ce1d9c552add@arm.com \
--to=luis.machado@arm.com \
--cc=Kavitha.Natarajan@amd.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=nickc@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).