public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug exp/20991] __int128 type support Date: Sat, 25 Feb 2023 01:15:03 +0000 [thread overview] Message-ID: <bug-20991-4717-WztwfXhn00@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 #16 from Tom Tromey <tromey at sourceware dot org> --- Yeah. I even considered just writing our own. Monday or so I'll push my WIP patch to add wide-int to the tree and you can see what it looks like. A few hacks were needed, though nothing too serious. Mostly I couldn't be bothered to figure out how all the classes work. The main attraction of GMP is we already have it, and I recently added a few operators and such. For constants and values in type properties we can either just store the number on some obstack, or use LEB. The latter can be nice since we can sometimes just use a pointer directly into the DWARF data. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-25 1:15 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 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 [this message] 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-WztwfXhn00@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: 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).