public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug ada/31574] [gdb, armv8l] FAIL: gdb.ada/verylong.exp: print x
Date: Tue, 02 Apr 2024 14:14:31 +0000	[thread overview]
Message-ID: <bug-31574-4717-n4CkAB6WQy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31574-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31574

--- Comment #5 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d16a53152cc2dfd6e92fdf9ae288ff19dac49dd1

commit d16a53152cc2dfd6e92fdf9ae288ff19dac49dd1
Author: Tom de Vries <tdevries@suse.de>
Date:   Tue Apr 2 16:14:39 2024 +0200

    [gdb/testsuite] Fix gdb.ada/verylong.exp on 32-bit target

    In an aarch32-linux chroot on an aarch64-linux system, I run into:
    ...
    (gdb) print x^M
    $1 = 9223372036854775807^M
    (gdb) FAIL: gdb.ada/verylong.exp: print x
    ...

    A passing version on aarch64-linux looks like:
    ...
    (gdb) print x^M
    $1 = 170141183460469231731687303715884105727^M
    (gdb) PASS: gdb.ada/verylong.exp: print x
    ...

    The difference is caused by the size of the type Long_Long_Long_Integer,
which
    is:
    - a 128-bit signed on 64-bit targets, and
    - a 64-bit signed on 32-bit target.

    Fix this by detecting the size of the Long_Long_Long_Integer type, and
    handling it.

    Tested on aarch64-linux and aarch32-linux.

    Approved-By: Tom Tromey <tom@tromey.com>

    PR testsuite/31574
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31574

    [1]
https://gcc.gnu.org/onlinedocs/gnat_rm/Implementation-Defined-Characteristics.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-04-02 14:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29  7:51 [Bug ada/31574] New: " vries at gcc dot gnu.org
2024-03-29 11:53 ` [Bug ada/31574] " tromey at sourceware dot org
2024-03-29 11:57 ` vries at gcc dot gnu.org
2024-03-29 12:17 ` vries at gcc dot gnu.org
2024-03-29 12:38 ` vries at gcc dot gnu.org
2024-04-02 14:14 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-02 14:16 ` [Bug testsuite/31574] [gdb, 32-bit] " vries at gcc dot gnu.org

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=bug-31574-4717-n4CkAB6WQy@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).