public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jim at meyering dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13246] RFE: strtold: do not include uninitialized bytes when converting "NaN" Date: Thu, 06 Oct 2011 08:33:00 -0000 [thread overview] Message-ID: <bug-13246-131-Smm2WsXfwR@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13246-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13246 --- Comment #5 from jim at meyering dot net <jim at meyering dot net> 2011-10-06 08:32:36 UTC --- Hi Jakub, Thanks for commenting. I realize that this is not officially a bug. That's why I wrote "RFE: ...". However, is there some other way to avoid valgrind "warnings" about those stack bytes being used uninitialized? Alternatively, can you recommend a portable way to compare the valid bits of two NaN values? -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2011-10-06 8:33 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-01 17:39 [Bug libc/13246] New: " jim at meyering dot net 2011-10-05 14:52 ` [Bug libc/13246] " schwab@linux-m68k.org 2011-10-05 22:10 ` bugdal at aerifal dot cx 2011-10-06 7:57 ` schwab@linux-m68k.org 2011-10-06 8:16 ` jakub at redhat dot com 2011-10-06 8:33 ` jim at meyering dot net [this message] 2011-10-06 8:46 ` jakub at redhat dot com 2011-10-06 9:31 ` jim at meyering dot net 2011-10-06 9:41 ` schwab@linux-m68k.org 2011-10-06 9:48 ` jim at meyering dot net 2011-10-06 9:57 ` jakub at redhat dot com 2011-10-06 12:40 ` bugdal at aerifal dot cx 2014-06-27 11:59 ` fweimer at redhat dot com
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-13246-131-Smm2WsXfwR@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).