ee-as and iop-as

BaronChronos · Post by **BaronChronos** » Sat Jan 24, 2004 12:25 pm

I'm not entirely sure that this could be considered a bug, but if you call either ee-as or iop-as with a .vsm file as the input file and specify the output file (-o) with the same input file name, it completely overwrites the .vsm file with what appears to be executable code.

Example: ee-as file.vsm -o file.vsm

Yet if you specify a different file name as the output file, it complains about just about every opcode in the program, so I know the executable code it produces can't possibly be correct.

Anyway, just something I noticed.

-----------------------------------------------------------

Edit: my bad. I should've read the title of the forum a bit more closely. This is obviously in the wrong forum. Could some mod move this to the appropriate forum?

Post by **ooPo** » Sat Jan 24, 2004 3:08 pm

Neither ee-as or iop-as is going to compile VU code for you. That would be why it complains...

As for it overwriting itself but not complaining? That's just odd. :)

Post by **ooPo** » Sat Jan 24, 2004 3:09 pm

Moved to: EE Development

Post by **blackdroid** » Sat Jan 24, 2004 4:16 pm

I going to say that this is abit of default behaviour for as.
try as empty.c -o empty.c and you will get a 441 byte big file.
Its the generated elf header. So albeit abit odd behaviour, thats the way it is. dont specify input files as output files :)