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 exp/20991] __int128 type support
Date: Wed, 21 Jul 2021 12:19:56 +0000	[thread overview]
Message-ID: <bug-20991-4717-hWxvRLrLTH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20991-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from cvs-commit at gcc dot gnu.org <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=0057a7ee0d963eb9aee5cdfb9d6da5279bc8caf9

commit 0057a7ee0d963eb9aee5cdfb9d6da5279bc8caf9
Author: Tom de Vries <tdevries@suse.de>
Date:   Wed Jul 21 14:19:51 2021 +0200

    [gdb/testsuite] Add KFAILs for gdb.ada FAILs with gcc-11

    With gcc-11 we run into:
    ...
    (gdb) print pa_ptr.all^M
    That operation is not available on integers of more than 8 bytes.^M
    (gdb) KFAIL: gdb.ada/arrayptr.exp: scenario=all: print pa_ptr.all (PRMS:
gdb/20991)
    ...

    This is due to PR exp/20991 - "__int128 type support".  Mark this and
similar
    FAILs as KFAIL.

    Also mark this FAIL:
    ....
    (gdb) print pa_ptr(3)^M
    cannot subscript or call something of type `foo__packed_array_ptr'^M
    (gdb) FAIL: gdb.ada/arrayptr.exp: scenario=minimal: print pa_ptr(3)
    ...
    as a KFAIL for PR ada/28115 - "Support packed array encoded as
    DW_TAG_subrange_type".

    Tested on x86_64-linux, with gcc-10 and gcc-11.

    gdb/testsuite/ChangeLog:

    2021-07-21  Tom de Vries  <tdevries@suse.de>

            * gdb.ada/arrayptr.exp: Add KFAILs for PR20991 and PR28115.
            * gdb.ada/exprs.exp: Add KFAILs for PR20991.
            * gdb.ada/packed_array_assign.exp: Same.

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

  parent reply	other threads:[~2021-07-21 12:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-20991-4717@http.sourceware.org/bugzilla/>
2020-04-10  0:21 ` ssbssa at sourceware dot org
2021-07-21 12:19 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-21 12:22 ` cvs-commit at gcc dot gnu.org
2023-02-23 16:37 ` tromey at sourceware dot org
2023-02-23 16:44 ` tromey at sourceware dot org
2023-02-23 19:40 ` pedro at palves dot net
2023-02-23 21:08 ` tromey at sourceware dot org
2023-02-24 10:55 ` pedro at palves dot net
2023-02-24 12:35 ` pedro at palves dot net
2023-02-24 14:46 ` tromey at sourceware dot org
2023-02-24 16:13 ` tromey at sourceware dot org
2023-02-24 23:21 ` pedro at palves dot net
2023-02-25  1:15 ` tromey at sourceware dot org
2023-02-27 18:01 ` tromey at sourceware dot org
2023-02-28 19:31 ` tromey at sourceware dot org
2023-03-01 21:51 ` tromey at sourceware dot org
2023-03-01 21:51 ` tromey at sourceware dot org
2023-03-01 21:51 ` tromey at sourceware dot org
2023-03-01 21:56 ` tromey at sourceware dot org
2023-03-01 21:57 ` tromey at sourceware dot org
2023-03-01 21:59 ` tromey at sourceware dot org
2023-03-01 22:01 ` tromey at sourceware dot org
2023-03-01 22:01 ` [Bug exp/20991] [meta] " tromey at sourceware dot org
2023-03-27 14:26 ` tromey at sourceware dot org
2023-04-17 17:05 ` tromey at sourceware dot org
2023-04-17 17:05 ` tromey at sourceware dot org
2024-03-20 17:26 ` ssbssa at sourceware dot 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-20991-4717-hWxvRLrLTH@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).