public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/16381] [3.3/3.5 Regression] Structure layout bug
Date: Tue, 17 Aug 2004 06:39:00 -0000 [thread overview]
Message-ID: <20040817063936.19611.qmail@sourceware.org> (raw)
In-Reply-To: <20040706091123.16381.zhangjie@magima.com.cn>
------- Additional Comments From mmitchel at gcc dot gnu dot org 2004-08-17 06:39 -------
It's my opinion that GCC 3.4.x is correct, and 3.5 is wrong.
Jie's suggestion that Quad have alignment 4 does not make sense to me, given the
"__attribute__ ((aligned (16)))" on its member "x".
The distinction between GCC 3.4 and GCC 3.5 is that GCC 3.4 is treating Base2 as
a POD, where as GCC 3.5 is not. I see no reason why a struct containing
"__m128" should disqualify a type from being a POD, although clearly that is not
specified by the standard.
Therefore, I've retargeted this at GCC 3.5.
--
What |Removed |Added
----------------------------------------------------------------------------
Known to fail|3.3.4 3.4.0 3.5.0 |3.3.4 3.5.0
Summary|[3.3/3.4/3.5 Regression] |[3.3/3.5 Regression]
|Structure layout bug |Structure layout bug
Target Milestone|3.4.2 |3.5.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16381
next prev parent reply other threads:[~2004-08-17 6:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 9:11 [Bug c++/16381] New: " zhangjie at magima dot com dot cn
2004-07-06 15:42 ` [Bug c++/16381] " pinskia at gcc dot gnu dot org
2004-08-16 10:47 ` [Bug c++/16381] [3.3/3.4/3.5 Regression] " giovannibajo at libero dot it
2004-08-17 6:39 ` mmitchel at gcc dot gnu dot org [this message]
2004-08-17 7:31 ` [Bug c++/16381] [3.3/3.5 " zhangjie at magima dot com dot cn
2004-08-17 9:53 ` zhangjie at magima dot com dot cn
2004-08-17 10:04 ` zhangjie at magima dot com dot cn
2004-10-28 6:00 ` [Bug c++/16381] [3.3/4.0 " mmitchel at gcc dot gnu dot org
2004-10-28 6:18 ` mmitchel at gcc dot gnu dot org
2004-10-28 7:14 ` dannysmith at users dot sourceforge dot net
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=20040817063936.19611.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).