public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: Tom Tromey <tromey@adacore.com>
Cc: 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: Tue, 12 Mar 2024 17:57:20 +0400	[thread overview]
Message-ID: <7F624528-A1EA-464D-BC58-7499F5E0C608@linaro.org> (raw)
In-Reply-To: <87zfv4o79d.fsf@tromey.com>

> On Mar 12, 2024, at 00:14, Tom Tromey <tromey@adacore.com> wrote:
> 
>>>>>> 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

Ah, now I understand.  While we do have the above commit in our GCC sources (we build tip-of-trunk in this CI configuration), we don't enable ada language.  So testsuite harness detects GCC version as 14.0 and enables the test, but actual gnat compiler is used from the distro package, which is much older.

We will consider enabling ada language in our CI builds, which should fix this.

Thanks for helping troubleshooting this!

--
Maxim Kuvyrkov
https://www.linaro.org



      reply	other threads:[~2024-03-12 13:57 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
2024-03-12 13:57     ` Maxim Kuvyrkov [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=7F624528-A1EA-464D-BC58-7499F5E0C608@linaro.org \
    --to=maxim.kuvyrkov@linaro.org \
    --cc=gdb-testers@sourceware.org \
    --cc=linaro-toolchain@lists.linaro.org \
    --cc=tromey@adacore.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).