search for: format0

...gt; struct type. Perhaps it doesn't matter, because we will hopefully be > moving to per-bit encoding in the near future. I don't thinkits worth it at this point. We have way more serious things going on than an extra byte for a type. Consider that all ICmp/FCmp instructions will use format0 (the largest) in anything but the smallest of functions (less than 64 instructions). This will get naturally cleaned up when we move to bit streams. If you *really* want to be efficient, the *right* way to do this is to create a new TypeID and the corresponding class (class PackedStructureType :...

On Dec 6, 2006, at 10:44 AM, Andrew Lenharth wrote: > Currently, Structure layout is left to targets, which implement them > according to the ABI of that platform. While this is fine for most > structures, it makes packed structures very ugly. All fields in a > packed type must be converted to byte arrays with casts to access > fields, which bloats accesses and obsfucates the

Currently, Structure layout is left to targets, which implement them according to the ABI of that platform. While this is fine for most structures, it makes packed structures very ugly. All fields in a packed type must be converted to byte arrays with casts to access fields, which bloats accesses and obsfucates the types. First class support for packed types would clean up the generated code