objcopy behavior question on non-octet targets

[Joel Sherrill <joel dot sherrill at OARcorp dot com>]

Hi,

I tried converting a binary file to a .o in order to link
it into an executable. I use this trick to include things
like tar images in executables.  It works as expected on
"normal CPUs " that are byte-addressable.

On the TI C3x/C4x (target=c4x-rtems == c4x-coff), the size
of the resulting object file was 4x that of the binary image.
I assume this is because each byte in the binary file becomes
one 32 bit word in the coff file.

I was hoping it would end up being packed denser than this.
I don't know what the behavior should be and suspect that there
is no right answer.  The file created is technically an array
of unsigned chars so I understand how the output is correct
based on this interpretation.

I would like to hear others opinions on what is useful/correct/expected.


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985