public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jwakely dot gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/30111] Value-initialization of POD base class doesn't initialize members
Date: Mon, 18 Jun 2007 01:37:00 -0000 [thread overview]
Message-ID: <20070618013656.18797.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30111-5876@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from jwakely dot gcc at gmail dot com 2007-06-18 01:36 -------
Confirmed on x86-linux, sparc-solaris and ppc-AIX so I've removed the Target.
Also verified that valgrind shows the uninitialised memory reads.
This bug breaks common idioms like:
template <typename A, typename B>
struct compressed_pair : A {
compressed_pair() : A(), second_() { }
A& first() { return *this; }
B& second() { return second_; }
private:
B second_;
};
--
jwakely dot gcc at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
GCC target triplet|sparc-sun-solaris2.9 |
Known to fail| |4.2.0 4.1.1 3.4.3 3.3.4
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30111
next prev parent reply other threads:[~2007-06-18 1:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 17:51 [Bug c++/30111] New: " gcc-bugzilla at kayari dot org
2006-12-07 18:03 ` [Bug c++/30111] " gcc-bugzilla at kayari dot org
2006-12-08 7:27 ` rguenth at gcc dot gnu dot org
2006-12-08 7:35 ` pinskia at gcc dot gnu dot org
2006-12-08 10:36 ` gcc-bugzilla at kayari dot org
2006-12-30 19:40 ` gdr at gcc dot gnu dot org
2007-06-10 2:18 ` pinskia at gcc dot gnu dot org
2007-06-18 1:37 ` jwakely dot gcc at gmail dot com [this message]
2008-02-04 16:07 ` rguenth at gcc dot gnu dot org
2009-02-11 5:35 ` jason at gcc dot gnu dot org
2009-02-11 22:39 ` jason at gcc dot gnu dot org
2009-02-11 22:50 ` jason at gcc dot gnu dot org
[not found] <bug-30111-4@http.gcc.gnu.org/bugzilla/>
2014-02-16 10:02 ` jackie.rosen at hushmail 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=20070618013656.18797.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).