public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michael dot haubenwallner at salomon dot at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29209] ICE optimizing passing long double to abstract method while in other abstract's impl
Date: Tue, 26 Sep 2006 07:28:00 -0000 [thread overview]
Message-ID: <20060926072836.8088.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29209-9385@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from michael dot haubenwallner at salomon dot at 2006-09-26 07:28 -------
Err, the patch from Bug#26957#c16 is already applied and works.
This is another ICE.
Difference in testcase is that the second ICE occurs when the 'long double
value' is passed to another virtual method of another abstract objectptr.
In the first one, the body of DataOutputStream_impl::write_longdouble() is
empty, while here it is not.
And, the second one does occur with any optimization >= -O1, not with -O0.
--
michael dot haubenwallner at salomon dot at changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|DUPLICATE |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29209
next prev parent reply other threads:[~2006-09-26 7:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 9:00 [Bug c++/29209] New: " michael dot haubenwallner at salomon dot at
2006-09-25 9:02 ` [Bug c++/29209] " michael dot haubenwallner at salomon dot at
2006-09-26 7:10 ` pinskia at gcc dot gnu dot org
2006-09-26 7:28 ` michael dot haubenwallner at salomon dot at [this message]
2006-10-10 23:01 ` danglin at gcc dot gnu dot org
2007-02-03 9:45 ` tbm at cyrius dot com
2007-02-03 14:48 ` dave at hiauly1 dot hia dot nrc dot ca
2007-02-03 15:16 ` dave at hiauly1 dot hia dot nrc dot ca
2007-02-04 1:51 ` dave at hiauly1 dot hia dot nrc dot ca
2007-10-19 21:10 ` tbm at cyrius dot com
2007-10-19 21:13 ` tbm at cyrius dot com
2007-11-07 2:49 ` dave at hiauly1 dot hia dot nrc dot ca
2009-05-05 17:54 ` sje at cup dot hp 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=20060926072836.8088.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).