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 cli/16242] print format for hex float
Date: Sat, 06 Jun 2020 14:58:27 +0000	[thread overview]
Message-ID: <bug-16242-4717-ijM1qkSVx4@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16242-4717@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Tom Tromey <tromey at sourceware dot org> ---
This has been filed a few times; I'm picking this one as the canonical
bug since it mentions the /z thing.

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

  reply	other threads:[~2020-06-06 14:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 18:49 [Bug cli/16242] New: " schwab@linux-m68k.org
2020-06-06 14:58 ` tromey at sourceware dot org [this message]
2020-06-06 14:58 ` [Bug cli/16242] " tromey at sourceware dot org
2020-06-06 14:59 ` tromey at sourceware dot org
2020-06-06 14:59 ` tromey at sourceware dot org
2020-06-06 16:02 ` schwab@linux-m68k.org
2020-06-07 16:35 ` tromey at sourceware dot org
2020-06-07 17:32 ` b7.10110111 at gmail dot com
2020-06-07 17:49 ` tromey at sourceware dot org
2022-02-17 18:49 ` tromey at sourceware dot org
2022-02-17 18:57 ` tromey at sourceware dot org
2022-02-17 20:15 ` tromey at sourceware dot org
2022-02-17 21:30 ` tromey at sourceware dot org
2022-02-18 16:53 ` tromey at sourceware dot org
2022-03-10 20:37 ` cvs-commit at gcc dot gnu.org
2022-03-10 20:38 ` tromey at sourceware dot org
2022-03-10 20:49 ` schwab@linux-m68k.org
2022-03-13  4:37 ` brobecker at gnat dot com
2022-05-07 15:38 ` tromey at sourceware dot org
2022-06-02 11:25 ` nchatz314 at gmail dot com
2023-08-31 16:47 ` tromey at sourceware dot org
2024-01-12 19:51 ` 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-16242-4717-ijM1qkSVx4@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).