public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/60407] call of overloaded ‘isnan’ is ambiguous
Date: Tue, 04 Mar 2014 11:12:00 -0000	[thread overview]
Message-ID: <bug-60407-4-FvWl8eq86r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60407-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60407

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(Tobias, see the URL field)

Reduced:

#include <math.h>
#include <cmath>

using namespace std;

int main()
{
  double d = 1.0;
  return isnan(d);
}


isnan.cc: In function ‘int main()’:
isnan.cc:9:17: error: call of overloaded ‘isnan(double&)’ is ambiguous
   return isnan(d);
                 ^
isnan.cc:9:17: note: candidates are:
In file included from /usr/include/features.h:364:0,
                 from /usr/include/math.h:26,
                 from isnan.cc:1:
/usr/include/bits/mathcalls.h:234:1: note: int isnan(double)
 __MATHDECL_1 (int,isnan,, (_Mdouble_ __value)) __attribute__ ((__const__));
 ^
In file included from isnan.cc:2:0:
/usr/include/c++/4.8.2/cmath:626:3: note: constexpr bool std::isnan(long
double)
   isnan(long double __x)
   ^
/usr/include/c++/4.8.2/cmath:622:3: note: constexpr bool std::isnan(double)
   isnan(double __x)
   ^
/usr/include/c++/4.8.2/cmath:618:3: note: constexpr bool std::isnan(float)
   isnan(float __x)
   ^
>From gcc-bugs-return-445377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Mar 04 11:14:06 2014
Return-Path: <gcc-bugs-return-445377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8933 invoked by alias); 4 Mar 2014 11:14:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8887 invoked by uid 48); 4 Mar 2014 11:14:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/60407] [=?UTF-8?Q?C++11call of overloaded ‘isnan’ is ambiguous?Date: Tue, 04 Mar 2014 11:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-60407-4-gcM0p5igSP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60407-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60407-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-03/txt/msg00246.txt.bz2
Content-length: 745

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60407

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|call of overloaded ‘isnan’  |[C++11call of overloaded
                   |is ambiguous                |‘isnan’ is ambiguous

--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Dilawar Singh from comment #0)
> In a large project, I get the following trace. This, however, compiled with
> g++4.7.x. Flag -std=c++11 is enabled in both cases.

Are you sure?

I get the same result with GCC 4.7.4, but only with -std=c++11
>From gcc-bugs-return-445379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Mar 04 11:16:42 2014
Return-Path: <gcc-bugs-return-445379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15588 invoked by alias); 4 Mar 2014 11:16:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15418 invoked by uid 48); 4 Mar 2014 11:16:38 -0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60409] [4.9 Regression] [c++1y] ICE on valid with template function
Date: Tue, 04 Mar 2014 11:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo.carlini at oracle dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-60409-4-nfa621BWGX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60409-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60409-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-03/txt/msg00248.txt.bz2
Content-length: 513

http://gcc.gnu.org/bugzilla/show_bug.cgi?id`409

Paolo Carlini <paolo.carlini at oracle dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-03-04
   Target Milestone|---                         |4.9.0
     Ever confirmed|0                           |1


  parent reply	other threads:[~2014-03-04 11:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04  9:31 [Bug libstdc++/60407] New: " dilawar.s.rajput at gmail dot com
2014-03-04  9:36 ` [Bug libstdc++/60407] " pinskia at gcc dot gnu.org
2014-03-04  9:38 ` pinskia at gcc dot gnu.org
2014-03-04  9:39 ` redi at gcc dot gnu.org
2014-03-04 10:22 ` dilawar.s.rajput at gmail dot com
2014-03-04 10:23 ` dilawar.s.rajput at gmail dot com
2014-03-04 11:06 ` burnus at gcc dot gnu.org
2014-03-04 11:12 ` redi at gcc dot gnu.org [this message]
2014-03-04 11:21 ` [Bug libstdc++/60407] [C++11] " dilawar.s.rajput at gmail dot com
2014-03-04 13:37 ` glisse at gcc dot gnu.org
2014-03-04 20:34 ` glisse at gcc dot gnu.org
2014-03-04 20:43 ` dilawar.s.rajput at gmail dot com
2015-06-15 23:04 ` eugene.zelenko at gmail 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-60407-4-FvWl8eq86r@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).