This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/8670] Alignment problem in std::basic_string
- From: "ncm-nospam at cantrip dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Jan 2005 05:29:45 -0000
- Subject: [Bug libstdc++/8670] Alignment problem in std::basic_string
- References: <20021121063601.8670.jkanze@caicheuvreux.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From ncm-nospam at cantrip dot org 2005-01-31 05:29 -------
Hmm, precisely two additional casts (or local unions), each in a
statement where a cast already appears, hardly seems like a "load".
But I'm always patient, right? It's just that anyplace a standard
construct could be used instead of an extension, I'll vote for the
standard one.
Question for the compiler jocks... why can unions enforce correct
alignment, but the __attribute__ form cannot? Can the extension
not be recast to generate what amounts to an unnamed union, and
thereby re-use the same machinery?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8670