public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/6718: Boost1.28 run-time problem
Date: Fri, 25 Oct 2002 14:46:00 -0000	[thread overview]
Message-ID: <20021025214602.32460.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/6718; it has been noted by GNATS.

From: Nathan Sidwell <nathan@codesourcery.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, pcarlini@unitus.it,
   gcc-bugs@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/6718: Boost1.28 run-time problem
Date: Fri, 25 Oct 2002 22:36:05 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6718
 
 this is a libstdc++ issue. <limits> appears to specialize
 template<> struct numeric_limits<double> to
 
      static double infinity() throw()
        { return __glibcpp_double_infinity; }
 
 and earlier,
 #ifndef __glibcpp_double_infinity
 #define __glibcpp_double_infinity 0.0
 #endif
 
 on the mainline this is significantly different, using __builtin_huge_val.
 
 nathan
 


             reply	other threads:[~2002-10-25 21:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 14:46 Nathan Sidwell [this message]
2002-10-27 13:55 paolo
2002-10-27 16:46 Gabriel Dos Reis
2002-10-28 11:56 Paolo Carlini
2002-10-31  9:10 paolo

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=20021025214602.32460.qmail@sources.redhat.com \
    --to=nathan@codesourcery.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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).