public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/31176] reorder class data members to minimize space waste
Date: Sat, 28 Apr 2007 00:37:00 -0000 [thread overview]
Message-ID: <20070428003723.12774.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31176-1186@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from pinskia at gcc dot gnu dot org 2007-04-28 01:37 -------
I think this needs a real specifications and not just saying the reording can
happen (as an asside there are two kinds of derived types in Fortran, one
called sequence and the other normal, the sequence one is what C/C++ does by
default and the normal one is more like what you want as reordering).
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-04-28 01:37:23
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31176
next prev parent reply other threads:[~2007-04-28 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 17:37 [Bug c++/31176] New: " sebor at roguewave dot com
2007-03-14 18:15 ` [Bug c++/31176] " fang at csl dot cornell dot edu
2007-03-14 18:16 ` pinskia at gcc dot gnu dot org
2007-03-14 19:04 ` sebor at roguewave dot com
2007-03-14 19:06 ` sebor at roguewave dot com
2007-03-14 19:09 ` pinskia at gcc dot gnu dot org
2007-03-15 19:54 ` sebor at roguewave dot com
2007-03-15 19:55 ` sebor at roguewave dot com
2007-03-15 23:51 ` sebor at roguewave dot com
2007-04-28 0:37 ` pinskia at gcc dot gnu dot org [this message]
[not found] <bug-31176-4@http.gcc.gnu.org/bugzilla/>
2014-09-03 0:56 ` richard-gccbugzilla at metafoo dot co.uk
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=20070428003723.12774.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).