This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libstdc++/8670] Alignment problem in std::basic_string


------- 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]