public inbox for src-cvs@sourceware.org help / color / mirror / Atom feed
From: brobecke@sourceware.org To: src-cvs@sourceware.org Subject: gdb and binutils branch master updated. 5af04e20f6333dc224d1668dcd433d7c8ca84e71 Date: Thu, 16 Oct 2014 21:52:00 -0000 [thread overview] Message-ID: <20141016215242.7759.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, master has been updated via 5af04e20f6333dc224d1668dcd433d7c8ca84e71 (commit) from 89c7137fad41711072e2a15ce539e2ad293bd065 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5af04e20f6333dc224d1668dcd433d7c8ca84e71 commit 5af04e20f6333dc224d1668dcd433d7c8ca84e71 Author: Joel Brobecker <brobecker@adacore.com> Date: Tue Oct 14 12:47:43 2014 -0400 Use strtod instead of strtold in libiberty/d-demangle.c strtold is currently used to decode templates which have a floating-point value encoded inside; but this routine is not available on some systems, such as Solaris 2.9 for instance. This patch fixes the issue by replace the use of strtold by strtod. It reduces a bit the precision, but it should still remain acceptable in most cases. libiberty/ChangeLog: * d-demangle.c: Replace strtold with strtod in global comment. (strtold): Remove declaration. (strtod): New declaration. (dlang_parse_real): Declare value as double instead of long double. Replace call to strtold by call to strtod. Update format in call to snprintf. ----------------------------------------------------------------------- Summary of changes: libiberty/ChangeLog | 9 +++++++++ libiberty/d-demangle.c | 10 +++++----- 2 files changed, 14 insertions(+), 5 deletions(-) hooks/post-receive -- gdb and binutils
reply other threads:[~2014-10-16 21:52 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141016215242.7759.qmail@sourceware.org \ --to=brobecke@sourceware.org \ --cc=src-cvs@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).