------- Comment #16 from dj at redhat dot com 2006-08-01 18:37 ------- I think it's acceptable to temporarily disable that assertion for this release, but (1) we should test that code on both big and little endian 64 bit machines and see if it produces wrong code (perhaps with a larger offset to see if the truncation is happening), and (2) we should consider re-enabling the assertion later if so.
Ideally, the assertion only detects the case where it *will* produce wrong code, at least on a big endian machine. That might imply that more special cases are needed for what is truly a no-op conversion, or an extra optimization step before we check the initializers. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27724
