public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/4586] printf crashes on some 'long double' values
Date: Tue, 22 Sep 2020 14:24:34 +0000	[thread overview]
Message-ID: <bug-4586-131-AGk6tpC13c@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-4586-131@http.sourceware.org/bugzilla/>

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

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://sourceware.org/bugz
                   |                            |illa/show_bug.cgi?id=26649

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

  parent reply	other threads:[~2020-09-22 14:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-4586-131@http.sourceware.org/bugzilla/>
2014-07-04 16:25 ` fweimer at redhat dot com
2020-03-16 16:54 ` cvs-commit at gcc dot gnu.org
2020-09-22 14:24 ` fweimer at redhat dot com [this message]
2021-09-21  0:53 ` cvs-commit at gcc dot gnu.org
2023-07-25 13:26 ` carlos at redhat dot com
2023-07-25 14:07 ` siddhesh at sourceware dot org
2007-06-02 23:29 [Bug libc/4586] New: " bruno at clisp dot org
2007-06-03  9:37 ` [Bug libc/4586] " schwab at suse dot de
2007-07-07 19:59 ` cvs-commit at gcc dot gnu dot org
2007-07-07 20:00 ` cvs-commit at gcc dot gnu dot org
2007-07-12 13:31 ` cvs-commit at gcc dot gnu dot org
2007-07-12 15:30 ` cvs-commit at gcc dot gnu 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-4586-131-AGk6tpC13c@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).