public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com> To: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org> Cc: tromey@adacore.com, gdb-testers@sourceware.org, Linaro Toolchain Working Group <linaro-toolchain@lists.linaro.org> Subject: Re: [Linaro-TCWG-CI] gdb-14-branchpoint-1356-g7737b133640: FAIL: 1 regressions on arm Date: Mon, 11 Mar 2024 14:14:54 -0600 [thread overview] Message-ID: <87zfv4o79d.fsf@tromey.com> (raw) In-Reply-To: <29B97042-BA6A-4EFB-8999-F4D35D8F1FC9@linaro.org> (Maxim Kuvyrkov's message of "Mon, 11 Mar 2024 19:56:19 +0400") >>>>> Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org> writes: >> | commit gdb-14-branchpoint-1356-g7737b133640 >> | Author: Tom Tromey <tromey@adacore.com> >> | Date: Tue Jan 9 11:47:17 2024 -0700 >> | >> | Handle DW_AT_endianity on enumeration types >> | >> | A user found that gdb would not correctly print a field from an Ada >> | record using the scalar storage order feature. We tracked this down >> | to a combination of problems. >> | >> | First, GCC did not emit DW_AT_endianity on the enumeration type. >> | ... 14 lines of the commit log omitted. > I see the above failure for both aarch64-linux-gnu and > arm-linux-gnueabihf in our testing. The log shows ([1]): > (gdb) PASS: gdb.ada/scalar_storage.exp: print V_LE > get_compiler_info: gcc-14-0-1 > Any idea what can be causing this? > This failure happens in CI configurations where we track tip-of-trunk GCC. This failure is what I would expect if your compiler does not have the fix. Can you see if your gcc includes this change? commit 5d8b60effc7268448a94fbbbad923ab6871252cd Author: Eric Botcazou <ebotcazou@adacore.com> Date: Wed Jan 10 13:23:46 2024 +0100 Fix debug info for enumeration types with reverse Scalar_Storage_Order This implements the support of DW_AT_endianity for enumeration types because they are scalar and therefore, reverse Scalar_Storage_Order is supported for them, but only when the -gstrict-dwarf switch is not passed because this is an extension. There is an associated GDB patch to be submitted to grok the new DWARF. thanks, Tom
next prev parent reply other threads:[~2024-03-11 20:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-27 13:25 ci_notify 2024-03-11 15:56 ` Maxim Kuvyrkov 2024-03-11 20:14 ` Tom Tromey [this message] 2024-03-12 13:57 ` Maxim Kuvyrkov
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=87zfv4o79d.fsf@tromey.com \ --to=tromey@adacore.com \ --cc=gdb-testers@sourceware.org \ --cc=linaro-toolchain@lists.linaro.org \ --cc=maxim.kuvyrkov@linaro.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: linkBe 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).