public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug exp/20991] __int128 type support
Date: Fri, 10 Apr 2020 00:21:30 +0000	[thread overview]
Message-ID: <bug-20991-4717-k4pSanL9Hj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20991-4717@http.sourceware.org/bugzilla/>

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

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ssbssa at sourceware dot org

--- Comment #4 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Tom Tromey from comment #0)
> I tried a couple experiments with __int128 and found some gdb issues.
> 
> My test code:
> 
> __int128 x = 72;
> 
> I compiled with -g -c then ran gdb on the .o.
> 
> Printing kind of works, but chooses hex by default and zero-pads:
> 
> (gdb) p x
> $1 = 0x00000000000000000000000000000048
> 
> Specifying decimal still zero-pads, which looks very weird:
> 
> (gdb) p/d x
> $2 = 00000000000000000000000000000072
> 
> Addition doesn't work:
> 
> (gdb) p x + 5
> That operation is not available on integers of more than 8 bytes.

There is no longer zero-padding since 8.1, but addition still doesn't work.

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

       reply	other threads:[~2020-04-10  0:21 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 [this message]
2021-07-21 12:19 ` cvs-commit at gcc dot gnu.org
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-k4pSanL9Hj@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).