public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/31780] [4.2/4.3 regression] ICE with incompatible types for ?: with "complex type" conversion
Date: Mon, 07 Jan 2008 08:01:00 -0000 [thread overview]
Message-ID: <20080107074444.7570.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31780-1771@http.gcc.gnu.org/bugzilla/>
------- Comment #30 from mark at codesourcery dot com 2008-01-07 07:44 -------
Subject: Re: [4.2/4.3 regression] ICE with incompatible types
for ?: with "complex type" conversion
gdr at cs dot tamu dot edu wrote:
> | Is it conceivable that ISO C++ will ever add a
> | complex<double>::complex(int) constructor that doesn't set the real part
> | to the value of the argument (converted to double), and the imaginary
> | part to zero?
>
> That isn't the issue. My concern is whether ISO C++ will ever
> change conversion rules, say from integers to floats or doubles. The
> answer is likely.
What's the likely change?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31780
next prev parent reply other threads:[~2008-01-07 7:45 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 23:50 [Bug c++/31780] New: [4.3 regression] ICE with incompatible types for ?: reichelt at gcc dot gnu dot org
2007-05-01 23:51 ` [Bug c++/31780] " reichelt at gcc dot gnu dot org
2007-05-02 0:46 ` [Bug c++/31780] [4.3 regression] ICE with incompatible types for ?: with "complex type" conversion pinskia at gcc dot gnu dot org
2007-05-02 0:47 ` pinskia at gcc dot gnu dot org
2007-06-29 18:28 ` mmitchel at gcc dot gnu dot org
2007-07-07 10:47 ` [Bug c++/31780] [4.2/4.3 " reichelt at gcc dot gnu dot org
2007-07-07 19:26 ` mmitchel at gcc dot gnu dot org
2007-07-07 19:35 ` mmitchel at gcc dot gnu dot org
2007-07-07 22:13 ` mmitchel at gcc dot gnu dot org
2007-07-07 22:21 ` mmitchel at gcc dot gnu dot org
2007-07-07 22:44 ` pcarlini at suse dot de
2007-07-07 22:51 ` mark at codesourcery dot com
2007-07-07 22:57 ` pcarlini at suse dot de
2007-07-08 18:12 ` mark at codesourcery dot com
2007-07-08 18:42 ` pcarlini at suse dot de
2007-07-08 18:58 ` mmitchel at gcc dot gnu dot org
2007-07-20 3:49 ` mmitchel at gcc dot gnu dot org
2007-10-09 19:22 ` mmitchel at gcc dot gnu dot org
2007-12-16 23:26 ` steven at gcc dot gnu dot org
2007-12-18 5:36 ` mmitchel at gcc dot gnu dot org
2007-12-23 21:22 ` gdr at gcc dot gnu dot org
2007-12-26 21:19 ` mark at codesourcery dot com
2007-12-26 22:03 ` pcarlini at suse dot de
2008-01-05 8:13 ` gdr at cs dot tamu dot edu
2008-01-05 9:25 ` gdr at cs dot tamu dot edu
2008-01-05 9:32 ` mark at codesourcery dot com
2008-01-06 17:03 ` gdr at cs dot tamu dot edu
2008-01-06 21:45 ` mark at codesourcery dot com
2008-01-07 1:44 ` gdr at cs dot tamu dot edu
2008-01-07 1:47 ` mark at codesourcery dot com
2008-01-07 7:49 ` gdr at cs dot tamu dot edu
2008-01-07 7:49 ` gdr at cs dot tamu dot edu
2008-01-07 7:49 ` gdr at cs dot tamu dot edu
2008-01-07 8:01 ` mark at codesourcery dot com [this message]
2008-01-07 8:16 ` mark at codesourcery dot com
2008-01-07 9:48 ` gdr at cs dot tamu dot edu
2008-01-07 9:48 ` gdr at cs dot tamu dot edu
2008-01-07 16:46 ` mark at codesourcery dot com
2008-01-08 8:38 ` gdr at cs dot tamu dot edu
2008-01-08 8:43 ` mark at codesourcery dot com
2008-01-22 16:01 ` jason at gcc dot gnu dot org
2008-01-22 18:05 ` mark at codesourcery dot com
2008-01-25 16:52 ` rguenth at gcc dot gnu dot org
2008-01-25 18:54 ` jason at gcc dot gnu dot org
2008-01-25 20:14 ` jason at gcc dot gnu dot org
2008-01-25 20:17 ` [Bug c++/31780] [4.2 " jason 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=20080107074444.7570.qmail@sourceware.org \
--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).